Log inSubmit server
PlanVortex logo

PlanVortex

PlanVortex MCP server schedules posts, manages inboxes, and reads social media metrics across connected networks.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install PlanVortex

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "planvortex": {
      "command": "npx",
      "args": [
        "-y",
        "planvortex-mcp"
      ],
      "env": {
        "PLANVORTEX_CLIENT_ID": "YOUR_VALUE_HERE",
        "PLANVORTEX_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "PLANVORTEX_ORGANIZATION_ID": "YOUR_VALUE_HERE",
        "PLANVORTEX_MCP_ALLOW_AI": "YOUR_VALUE_HERE",
        "PLANVORTEX_MCP_READ_ONLY": "YOUR_VALUE_HERE",
        "PLANVORTEX_MCP_AUTH_TOKEN": "YOUR_VALUE_HERE",
        "PLANVORTEX_MCP_UPLOAD_DIRS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

PlanVortex MCP server connects an AI assistant to PlanVortex, letting it schedule publications, inspect comments and conversations, and send replies across connected social networks. It runs through npx in stdio mode, with optional HTTP and hosted deployment modes. Use it when an agent needs controlled access to publishing workflows, inbox management, account metrics, or PlanVortex's AI planning features. Creating AI plans is opt-in, while read-only mode can remove write tools.

Use cases

  • Schedule social publications across connected networks
  • Review unread comments and private messages
  • Reply to comments and send inbox messages
  • Inspect publication and account performance
  • Generate draft content plans from themes or products

Key features

  • Multi-network publication scheduling
  • Comment and private-message management
  • Publication and account analytics
  • Optional AI plan generation
  • Read-only operating mode
  • Stdio and self-hosted HTTP modes

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

6/6 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · planvortex-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.9kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.

How PlanVortex works

What PlanVortex does

PlanVortex MCP server exposes PlanVortex account and social-media operations to compatible MCP clients. It can work with connected accounts on Facebook, Instagram, Threads, LinkedIn, TikTok, X, WhatsApp, YouTube, Google Business, Bluesky, Discord, Telegram, Slack, and Pinterest.

The server supports the 🌐 Social Media category through tools for scheduled publishing, comment moderation, private-message handling, media uploads, reporting, and account context. It also provides prompts for weekly planning, inbox triage, and turning a brief into a publication. Four resources supply network limits, supported capabilities, comment behavior, and organization information.

How it works

An MCP client starts the package with npx, and the process authenticates to PlanVortex using an application client ID and client secret. The organization ID is optional; supplying it can avoid an extra lookup during a conversation. The server then exposes tools that operate on the organizations and social accounts available through PlanVortex.

Reading tools cover organizations, accounts, plan usage, unread counts, publications, comments, conversations, messages, social limits, capabilities, and performance statistics. Write operations include creating or updating publications, replying to comments, hiding comments, marking comments read, sending messages, retrying publications, and uploading media.

PlanVortex MCP server can also submit an AI plan based on a theme, images, an article, or products from a connected WooCommerce store. The request queues work rather than returning finished posts immediately. The agent must poll for the result, and generated content remains in draft form until a person decides whether to schedule each publication.

Setup and configuration

A PlanVortex app is required. Create its credentials in the PlanVortex panel under Settings → Apps, then provide them to the MCP client. A basic stdio configuration uses:

  • PLANVORTEX_CLIENT_ID
  • PLANVORTEX_CLIENT_SECRET
  • PLANVORTEX_ORGANIZATION_ID (optional)

For Claude Code, the same values can be passed with claude mcp add. The package starts in stdio mode by default. Self-hosted HTTP deployment requires the --http flag; when binding beyond localhost, set PLANVORTEX_MCP_AUTH_TOKEN. HTTP deployments should also place TLS in a reverse proxy.

AI plan creation is disabled unless PLANVORTEX_MCP_ALLOW_AI=1 is set. Read-only deployments can set PLANVORTEX_MCP_READ_ONLY=1, which removes the server's nine write tools from the listing.

Tools and capabilities

The tool groups include:

  • Context: organizations, accounts, plan usage, and unread totals.
  • Publishing: publication discovery, creation, updates, destinations, and retries.
  • Comments and messages: inbox listing, thread inspection, replies, moderation, and outbound messages.
  • AI planning: templates, store products, plan status, results, and optional plan creation.
  • Media and reporting: uploads, dashboard summaries, publication statistics, top publications, and account metrics.
  • Catalog and connection support: network limits, capabilities, and single-use account connection links.

The server marks read-only and write operations with MCP tool annotations. User-written comments, reviews, and incoming messages are presented as untrusted content rather than instructions.

Limitations and notes

PlanVortex MCP server does not delete posts, accounts, contacts, or comments. It also cannot complete social-account authorization itself. create_connect_link produces a single-use link that expires after fifteen minutes; a person must open it and complete the provider's authorization flow.

AI plan generation can consume account credits and is intentionally absent unless explicitly enabled. The resulting items are drafts, not automatically scheduled posts. Publishing, sending, overwriting, hiding, and credit-consuming operations can have external effects, so the MCP client's confirmation behavior remains relevant.

The HTTP mode keeps the client secret in the server process. Requests reaching a remotely bound process therefore need the configured authentication token, and the server validates the request origin. The hosted mode is a separate multi-user deployment operated by PlanVortex and uses PlanVortex-issued OAuth access tokens instead of local app credentials.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about PlanVortex

PlanVortex is an MCP server that connects AI assistants to PlanVortex and its connected social networks. Its main tools schedule publications, read and manage comments, inspect conversations, send messages, upload media, retrieve metrics, and optionally queue AI-generated content plans for connected accounts.

Install it by configuring your MCP client to run `npx -y planvortex-mcp`. Provide `PLANVORTEX_CLIENT_ID` and `PLANVORTEX_CLIENT_SECRET` from a PlanVortex app; `PLANVORTEX_ORGANIZATION_ID` is optional.

Yes, PlanVortex works with Cursor through an MCP configuration using the npx command and PlanVortex credentials. The README also names Claude Desktop, Claude Code, and VS Code as supported clients.

Enable it by setting `PLANVORTEX_MCP_ALLOW_AI=1` before starting the server. The `create_ai_plan` tool then becomes available, queues generation, and requires polling; its output is drafts rather than automatically scheduled posts.

Set `PLANVORTEX_MCP_READ_ONLY=1` when starting the server. This removes nine write tools from the tool listing, leaving the agent with read access rather than publishing or messaging actions.

Related MCP servers

All in Social Media All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPlanVortex AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/planvortex?style=directory)](https://allmcps.com/mcp/planvortex)
HTML Embed
<a href="https://allmcps.com/mcp/planvortex"><img src="https://allmcps.com/api/badge/planvortex?style=directory" alt="PlanVortex on AllMCPs" /></a>