Programa publicaciones en redes sociales, gestiona comentarios y responde mensajes privados en múltiples redes sociales utilizando un asistente de IA.
También conocido como taliasoftworks/PlanVortexMCP, planvortexmcp, planvortex-mcp
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.14.0
- Último commit
- 13 nov 2026
- Licencia
- MIT
¿Qué es PlanVortex MCP?
Programa publicaciones en redes sociales, gestiona comentarios y responde mensajes privados en múltiples redes sociales utilizando un asistente de IA.
Resumen generado a partir del README del proyecto
Acerca del MCP server de PlanVortex
PlanVortex permite a desarrolladores y gestores de redes sociales administrar su presencia en plataformas como Facebook, Instagram, TikTok y LinkedIn mediante asistentes de IA. Al conectarlo con clientes como Claude Desktop, Cursor o VS Code, puedes programar publicaciones, monitorear bandejas de comentarios y responder mensajes privados a través de una única interfaz. El servidor proporciona treinta y una herramientas especializadas para publicar, subir archivos multimedia y obtener métricas de cuenta o resúmenes de dashboards.
La configuración requiere una aplicación de PlanVortex con un client_id y un client_secret, que puedes generar en los ajustes de PlanVortex. Los usuarios pueden ejecutar el servidor localmente vía npx o desplegarlo usando un modo HTTP self-hosted. Para mayor seguridad, puedes habilitar un modo de solo lectura para restringir al asistente únicamente a la recuperación de datos. Si decides habilitar el planificador de IA configurando la variable de entorno allow_ai, el asistente puede transformar temas o catálogos de productos en borradores de publicaciones semanales, aunque esto consume créditos de cuenta y requiere confirmación manual antes de la programación.
Qué puedes hacer con él
- 1Programación automatizada de redes socialesPide a tu asistente de IA que cree y programe nuevas publicaciones en todas tus redes sociales conectadas.
- 2Gestión de bandeja de entrada y comentariosOrganiza la interacción en tus redes sociales leyendo comentarios no leídos y respondiendo a mensajes privados.
- 3Planificación de contenido impulsada por IAGenera una semana de borradores para redes sociales basados en un tema específico o un catálogo de productos.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar PlanVortex MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar PlanVortex MCP en Claude Code
$ claude mcp add --env 'PLANVORTEX_CLIENT_SECRET=<YOUR_PLANVORTEX_CLIENT_SECRET>' --env 'PLANVORTEX_CLIENT_ID=<PLANVORTEX_CLIENT_ID>' planvortexmcp -- npx -y planvortex-mcpInstalar PlanVortex MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"planvortexmcp": {
"command": "npx",
"args": [
"-y",
"planvortex-mcp"
],
"env": {
"PLANVORTEX_CLIENT_SECRET": "<YOUR_PLANVORTEX_CLIENT_SECRET>",
"PLANVORTEX_CLIENT_ID": "<PLANVORTEX_CLIENT_ID>"
}
}
}
}Instalar PlanVortex MCP en VS Code
.vscode/mcp.json
{
"servers": {
"planvortexmcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"planvortex-mcp"
],
"env": {
"PLANVORTEX_CLIENT_SECRET": "<YOUR_PLANVORTEX_CLIENT_SECRET>",
"PLANVORTEX_CLIENT_ID": "<PLANVORTEX_CLIENT_ID>"
}
}
}
}Instalar PlanVortex MCP en VS Code CLI
$ code --add-mcp '{"name":"planvortexmcp","type":"stdio","command":"npx","args":["-y","planvortex-mcp"],"env":{"PLANVORTEX_CLIENT_SECRET":"<YOUR_PLANVORTEX_CLIENT_SECRET>","PLANVORTEX_CLIENT_ID":"<PLANVORTEX_CLIENT_ID>"}}'Instalar PlanVortex MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"planvortexmcp": {
"command": "npx",
"args": [
"-y",
"planvortex-mcp"
],
"env": {
"PLANVORTEX_CLIENT_SECRET": "<YOUR_PLANVORTEX_CLIENT_SECRET>",
"PLANVORTEX_CLIENT_ID": "<PLANVORTEX_CLIENT_ID>"
}
}
}
}Instalar PlanVortex MCP en Codex
$ codex mcp add planvortexmcp --env 'PLANVORTEX_CLIENT_SECRET=<YOUR_PLANVORTEX_CLIENT_SECRET>' --env 'PLANVORTEX_CLIENT_ID=<PLANVORTEX_CLIENT_ID>' -- npx -y planvortex-mcpInstalar PlanVortex MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.planvortexmcp] command = "npx" args = ["-y", "planvortex-mcp"] [mcp_servers.planvortexmcp.env] PLANVORTEX_CLIENT_SECRET = "<YOUR_PLANVORTEX_CLIENT_SECRET>" PLANVORTEX_CLIENT_ID = "<PLANVORTEX_CLIENT_ID>"
Instalar PlanVortex MCP en Gemini CLI
$ gemini mcp add -s user -e 'PLANVORTEX_CLIENT_SECRET=<YOUR_PLANVORTEX_CLIENT_SECRET>' -e 'PLANVORTEX_CLIENT_ID=<PLANVORTEX_CLIENT_ID>' planvortexmcp npx -- -y planvortex-mcpInstalar PlanVortex MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"planvortexmcp": {
"command": "npx",
"args": [
"-y",
"planvortex-mcp"
],
"env": {
"PLANVORTEX_CLIENT_SECRET": "<YOUR_PLANVORTEX_CLIENT_SECRET>",
"PLANVORTEX_CLIENT_ID": "<PLANVORTEX_CLIENT_ID>"
}
}
}
}Configuración
PLANVORTEX_CLIENT_SECRETObligatorioSecretoSecret of that app.
PLANVORTEX_CLIENT_IDObligatorioClient id of a PlanVortex app. Every plan has apps, the free one included. Panel: Settings > Apps.
PLANVORTEX_MCP_ALLOW_AISet to 1 to add create_ai_plan, which generates a week of posts and spends AI credits.
PLANVORTEX_MCP_READ_ONLYSet to 1 to remove the nine write tools.
PLANVORTEX_MCP_UPLOAD_DIRSDirectories upload_media may read from. Empty means none.
PLANVORTEX_ORGANIZATION_IDDefault organization id. Optional: saves a discovery call per conversation.
| Nombre | Descripción | Tipo |
|---|---|---|
| PLANVORTEX_CLIENT_SECRET | Secret of that app. | ObligatorioSecreto |
| PLANVORTEX_CLIENT_ID | Client id of a PlanVortex app. Every plan has apps, the free one included. Panel: Settings > Apps. | Obligatorio |
| PLANVORTEX_MCP_ALLOW_AI | Set to 1 to add create_ai_plan, which generates a week of posts and spends AI credits. | |
| PLANVORTEX_MCP_READ_ONLY | Set to 1 to remove the nine write tools. | |
| PLANVORTEX_MCP_UPLOAD_DIRS | Directories upload_media may read from. Empty means none. | |
| PLANVORTEX_ORGANIZATION_ID | Default organization id. Optional: saves a discovery call per conversation. |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibletaliasoftworks/planvortexmcp is public and reachablegithub.com/taliasoftworks/planvortexmcp ↗Aprobado
- El paquete indica este repositorio como su origenplanvortex-mcp names taliasoftworks/planvortexmcp as sourcenpmjs.com/package/planvortex-mcp ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for planvortex-mcpnpmjs.com/package/planvortex-mcp/v/0.14.0#provenance ↗Aprobado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-13github.com/taliasoftworks/planvortexmcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from planvortex-mcpAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasthe package checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubplanvortex-mcp
The official Model Context Protocol server for PlanVortex. It lets an AI assistant — Claude Desktop, Claude Code, Cursor, VS Code — schedule posts, read the comment inbox and answer private messages across all your social networks: Facebook, Instagram, Threads, LinkedIn, TikTok, X, WhatsApp, YouTube, Google Business, Bluesky, Discord, Telegram, Slack and Pinterest.
You need a PlanVortex app, and every plan has them — the free one included. The server authenticates with a
client_idand aclient_secretthat you create in the PlanVortex panel under Settings → Apps. How many apps you get is what changes with the plan: 1 on Free, 2 on Basic, 5 on Pro, 10 on Custom.
Install
Nothing to install: your MCP client starts it with npx.
Claude Desktop, Cursor, VS Code
{
"mcpServers": {
"planvortex": {
"command": "npx",
"args": ["-y", "planvortex-mcp"],
"env": {
"PLANVORTEX_CLIENT_ID": "...",
"PLANVORTEX_CLIENT_SECRET": "...",
"PLANVORTEX_ORGANIZATION_ID": "optional, but saves a call per conversation"
}
}
}
}
Claude Code
claude mcp add planvortex \
--env PLANVORTEX_CLIENT_ID=... \
--env PLANVORTEX_CLIENT_SECRET=... \
-- npx -y planvortex-mcp
Then ask for something: "what do I have scheduled this week, and which comments are still unread?"
What it can do
Thirty-one tools, grouped by what they act on — and a thirty-second, create_ai_plan, that you
switch on yourself (see Generating with AI).
| Group | Tools |
|---|---|
| Context | list_organizations, list_accounts, get_plan_use, get_unread_counts |
| Publishing | list_publications, get_publication, list_destinations, create_publication, update_publication, retry_publication |
| AI planner | get_planner_templates, list_store_products, list_ai_plans, get_ai_plan, get_ai_plan_results, and create_ai_plan when enabled |
| Media | upload_media |
| Comments | list_comments, get_comment_thread, reply_to_comment, hide_comment, mark_comment_read |
| Messages | list_conversations, list_messages, send_message |
| Numbers | get_dashboard_summary, get_publication_stats, get_top_publications, get_account_metrics |
| Catalog | get_social_limits, get_social_capabilities, create_connect_link |
Plus three prompts — weekly_plan, inbox_triage, publish_from_brief — and four resources with
the per-network limits, capabilities, comment matrix and your organizations.
Generating with AI
PlanVortex does not just schedule what you wrote: it can write the week for you. Its planner
turns a theme, your own photos, an article or a connected shop's catalogue into a week of posts, and
get_planner_templates publishes the five templates with what each one costs. For a shop connected
to PlanVortex (a WooCommerce store), list_store_products finds the products to write about.
Reading is always available. Creating a plan is not, unless you switch it on:
"env": { "PLANVORTEX_MCP_ALLOW_AI": "1" }
That is deliberate, and it is about your money rather than your safety. Generating a plan spends AI
credits from your account, and an agent that retries in a loop is the worst possible caller for an
endpoint that bills. The protocol's own answer to this — asking you to confirm from inside the
server — is implemented by almost no client yet, so the confirmation is this line instead: a person
writes it once, before any agent starts. With it absent, create_ai_plan is not in the tool list at
all, so nothing can call it.
Two more things worth knowing. create_ai_plan does not return posts: it queues the plan and
returns the budget, and generation takes minutes — poll get_ai_plan. And what comes out are
drafts; scheduling them is still a person's decision, one post at a time, through
update_publication.
Two things it deliberately cannot do
It never deletes anything. No tool removes a post, an account, a contact or a comment. This is not a switch you can turn on; the code is not there. The reason is in the security section below.
It cannot connect a social account. Connecting Instagram is an OAuth flow with a person clicking
"authorize" on Meta's own screen, and an app with client credentials cannot do that — nobody's app
can. create_connect_link returns a single-use link that expires in fifteen minutes; hand it to the
user and let them open it.
Security
This server runs on your machine with your app's client_secret inside the process, and it feeds a
language model text that members of the public wrote — comments, reviews, DMs — while that same
model holds tools that publish under your brand.
That is a prompt-injection surface by construction, and it is worth knowing how it is handled:
- Every comment, review and incoming message arrives wrapped in an
untrusted_contentblock with an explicit notice that it is data, not instructions. It is not a guarantee — no wrapper is — but it raises the bar. - Nothing that deletes. If an injection succeeds, the worst case is a post you can see and delete, not four thousand deleted contacts.
- The tools that publish, send, overwrite, hide a comment or spend AI credits are annotated
destructiveHint: true, because none of that can be taken back once it is out, and the ones that only read arereadOnlyHint: true. Every tool carries all three hints explicitly. - Third-party text never enters a tool description or a cached resource, where your client would not mark it as untrusted.
- Whether a publish is confirmed by a human is decided by your MCP client, not by this server. The tools declare the annotations that make clients show the warning; keep them on.
Set PLANVORTEX_MCP_READ_ONLY=1 to remove the nine write tools from the listing entirely — useful
if you want to give an unsupervised agent read access and nothing else.
The --http mode
planvortex-mcp --http serves MCP over HTTP for a self-hosted deployment. The process holds your
client_secret, so anything that can reach the port can publish to your accounts with a plain
curl. Therefore:
- it binds to
127.0.0.1by default; - binding anywhere else requires
PLANVORTEX_MCP_AUTH_TOKENand the server refuses to start without it; - the
Originheader is validated on every request (DNS rebinding); - TLS is your reverse proxy's job — put one in front;
- and a token from the request is never forwarded to PlanVortex. It authenticates against this process and stops here.
docker run --rm -p 127.0.0.1:3000:3000 \
-e PLANVORTEX_CLIENT_ID=... -e PLANVORTEX_CLIENT_SECRET=... \
-e PLANVORTEX_MCP_AUTH_TOKEN=$(openssl rand -hex 32) \
planvortex-mcp --http --host 0.0.0.0
The flags are not optional there: the image speaks stdio by default, because that is what
an MCP client starts (docker run -i planvortex-mcp) and what a server directory introspects.
--http is the deployment mode, and you ask for it.
The --hosted mode
--hosted is the multi-user mode that PlanVortex runs itself, so that people can connect their
PlanVortex account to an assistant by signing in, with no app credentials. You do not need it to
self-host: that is --http. It holds no client_secret of any app, and it refuses to start if it
finds one, a default organization, PLANVORTEX_MCP_ALLOW_AI, PLANVORTEX_MCP_AUTH_TOKEN or
PLANVORTEX_MCP_UPLOAD_DIRS, because on a shared server those would apply to everybody.
Every request has to carry an OAuth access token issued by PlanVortex's Keycloak for this server
(its aud) and for one of the assistant clients it accepts (its azp). The server verifies it,
exchanges it for a token of its own (RFC 8693) and only that one reaches the API, so the token an
assistant stores never opens the PlanVortex API by itself. A request without a valid token gets a
401 whose WWW-Authenticate points at /.well-known/oauth-protected-resource. The scopes are
planvortex:read (required) and planvortex:write: without the second one the write tools are not
listed. Creating AI plans is not available in this mode, and neither is create_connect_link: a
connection link can only be issued to an app, so the user connects social accounts in the
PlanVortex panel and the server tells the model so.
Everything the server remembers between requests (the exchanged token, the list of organizations,
the duplicate guard and the rate limit) is kept per person, keyed by the token's sub. Run
planvortex-mcp --help for its environment variables.
Each request that gets past authentication logs one line when it ends: the sub, the assistant
client, the method, the tool and how it ended (with the PlanVortex error code if the API refused),
the HTTP status and the duration. Tool calls are logged at info and the rest at debug, and
nothing in the line is a token, an argument or a result.
Environment variables
| Variable | Required | What it does |
|---|---|---|
PLANVORTEX_CLIENT_ID |
yes | The app from your account. Every plan has apps. |
PLANVORTEX_CLIENT_SECRET |
yes | Its secret. Never passed as a tool argument. |
PLANVORTEX_ORGANIZATION_ID |
no | Default organization. Saves a discovery call per conversation. |
PLANVORTEX_BASE_URL |
no | Point at another PlanVortex deployment. |
PLANVORTEX_MCP_UPLOAD_DIRS |
no | Directories upload_media may read from. Empty means none. |
PLANVORTEX_MCP_AUTH_TOKEN |
with --http off-loopback |
Bearer token the HTTP endpoint requires. |
PLANVORTEX_MCP_READ_ONLY |
no | 1 removes the nine write tools. |
PLANVORTEX_MCP_ALLOW_AI |
no | 1 adds create_ai_plan, which spends AI credits. |
PLANVORTEX_MCP_LOG_LEVEL |
no | debug, info, warn, error, silent. Always to stderr. |
Uploading media
With stdio the server runs on your machine, so upload_media accepts an absolute local path —
but only inside PLANVORTEX_MCP_UPLOAD_DIRS, which is empty by default. Set it to the folders you
actually want reachable:
PLANVORTEX_MCP_UPLOAD_DIRS=/Users/you/Pictures,/Users/you/Downloads
Reading an arbitrary path is exactly what an injected prompt would ask for, so there is no way to
disable the allowlist. In --http mode a local path is refused outright: it would be a path on the
server, not on your machine. Pass a public https URL there.
Which organization?
Almost everything in PlanVortex hangs off an organization. The server resolves it in three steps:
the id_organization argument if the model passed one, then PLANVORTEX_ORGANIZATION_ID, and
finally — only if your app reaches exactly one — that one. If it reaches several and nothing says
which, the tool answers with the list of names and ids so the model can retry correctly, rather than
failing with a bare error.
Development
npm install
npm test # layers 1 and 2: no network, no credentials
npm run build
npm run inspector # MCP Inspector against the built server
Built on planvortex, the official Node client. This
server speaks no HTTP of its own: every call goes through the library, which is where the error
catalogue, the token cache, the multipart upload and the pagination already live.
Guides
Longer write-ups on planvortex.com:
- Posting to social media from your AI assistant with an MCP server: setup in each client, and how to connect it to Claude without installing anything
- LinkedIn MCP server: post from Claude through the official API
- Social media APIs for agentic workflows: the four things that decide it
- AI social posts from your own photos
- All articles
Links
MIT © Talia Softworks
Preguntas sobre PlanVortex MCP
¿Cómo agrego PlanVortex MCP a Claude Code?
Ejecuta claude mcp add --env 'PLANVORTEX_CLIENT_SECRET=<YOUR_PLANVORTEX_CLIENT_SECRET>' --env 'PLANVORTEX_CLIENT_ID=<PLANVORTEX_CLIENT_ID>' planvortexmcp -- npx -y planvortex-mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego PlanVortex MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué redes sociales soporta PlanVortex?
Soporta Facebook, Instagram, Threads, LinkedIn, TikTok, X, WhatsApp, YouTube, Google Business, Bluesky, Discord, Telegram, Slack y Pinterest.
¿Puede el servidor de IA eliminar mis publicaciones o comentarios en redes sociales?
No, el servidor está diseñado para que no pueda eliminar nada; no existe ninguna herramienta en el código para eliminar publicaciones, cuentas, contactos o comentarios.
¿Puede la IA conectar nuevas cuentas de redes sociales por mí?
No, la conexión de cuentas requiere un flujo de OAuth manual que una aplicación con credenciales de cliente no puede realizar.