PlanVortex vs Ravenpost
A side-by-side look at the PlanVortex and Ravenpost MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PlanVortex for social media work as a local process; choose Ravenpost for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose PlanVortex when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLANVORTEX_CLIENT_ID, PLANVORTEX_CLIENT_SECRET, PLANVORTEX_ORGANIZATION_ID, PLANVORTEX_MCP_ALLOW_AI, PLANVORTEX_MCP_READ_ONLY, PLANVORTEX_MCP_AUTH_TOKEN, PLANVORTEX_MCP_UPLOAD_DIRS. - You want tools like
list_organizations, list_accounts, get_plan_use.
Choose Ravenpost when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
list_workspaces, list_accounts, list_posts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 61/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | PLANVORTEX_CLIENT_IDPLANVORTEX_CLIENT_SECRETPLANVORTEX_ORGANIZATION_IDPLANVORTEX_MCP_ALLOW_AIPLANVORTEX_MCP_READ_ONLYPLANVORTEX_MCP_AUTH_TOKENPLANVORTEX_MCP_UPLOAD_DIRS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 31 | 21 |
| Full listing | View PlanVortex | View Ravenpost |
Tools & capabilities
PlanVortex tools 31
list_organizationsList the PlanVortex organizations this connection can reach, with their ids. Call this first when a tool says id_organization is required, or when the user names an organization you do not have an id for.list_accountsThe social accounts connected to an organization: network, name, follower count and whether the connection is broken. An account with error_code other than 0 cannot publish until a person reconnects it, and that is usually the answer to 'why did this post not go out'. On LinkedIn, personal_profile marks the person's own profile, as opposed to the pages they manage.get_plan_useWhat the organization's plan allows and what it has already used: accounts, storage and integrations. Check this before promising the user a connected account — a plan limit is not a transient error and retrying never fixes it. PUBLICATIONS ARE UNLIMITED on every plan: the count is reported for context and has no ceiling, so never refuse to schedule posts over it. What can stop a batch is rate — a per-hour cap per account and a daily cap per network, both in get_social_limits — and that one IS transient: waiting fixes it.get_unread_countsHow many comments and private messages are waiting, in one call. This is the 'what do I have today?' tool: start here, then use list_comments or list_conversations to see what they are.list_publicationsPosts of an organization, newest first, as a short projection: id, network, state, date and the first words of the text. States are draft, ready (scheduled), publishing, sended (published) and withErrors. Use get_publication for the full record of one, including why it failed.get_publicationThe full record of one post, including publication_errors — the list of reasons it did not go out. This is the tool to call when the user asks why a post failed.list_destinationsThe places INSIDE a connected account a post can be sent to: on Pinterest, the boards. Every Pinterest post needs one of these ids as destination_id in create_publication. Most networks have none — the account itself is where the post goes — and there this answers that it does not apply. Pass id_destination to get one board's sections. A SECRET board is seen by nobody else, so say so if the user picks one. Set refresh only for a board created a moment ago.create_publicationPublish now or schedule a post on ONE connected account. Pass state 'ready' with a future publish_date to schedule, or 'draft' to leave it for a person to review. Media has to be uploaded first with upload_media; pass the returned ids in files. The text is validated against the network's limits before anything is sent. On Pinterest a pin needs things no other network asks for: a board (destination_id, from list_destinations), at least one image or video — a pin is never text alone — and, if it should lead somewhere, the URL in link. On TikTok the user has to choose who can see the post (visibility), whether people can comment, Duet or Stitch (interactions) and whether it is commercial content; nothing may be preselected. Call this without them and the answer lists what that account allows, so you can ask. On YouTube, ask whether the video is made for kids. An Instagram video can come back in state publishing while the network processes it: that is not a failure, PlanVortex finishes it by itself within minutes, and creating it again would publish it twice. Always show the user what you are about to publish and let them confirm it: this posts publicly under their brand.update_publicationChange the text, media or scheduled date of a post that has NOT gone out yet (state draft or ready). A published post cannot be edited through PlanVortex; if you try, the error will say so. A Pinterest pin saved without a board (error 987) is fixed here by passing destination_id. On TikTok and YouTube the visibility and the other settings the user chose can be changed here too.retry_publicationAsk PlanVortex to try a failed post again (state withErrors only: a post in state publishing has not failed, it is still on its way). Read get_publication first: if it failed because the text is too long or the account is disconnected, retrying changes nothing until that is fixed. On Instagram, error 999 (the network ran out of time) is worth retrying; 998 (it rejected the file) is not, until the file changes.get_planner_templatesWhat an AI plan can be generated FROM, with the credits each template costs. Five of them: standard (a theme prompt, images generated by the model), from_images (the user's own photos, each with a description), from_text (an article by URL or pasted), from_catalog (products read live from a connected shop) and campaign (a countdown to a date, with a narrative arc). Read this before proposing a plan: the costs and the fields are prices, and they are not to be guessed or remembered. The ones that do not generate images cost a fraction — a week of 7 posts with a picture each is 519 credits on standard and 48 on from_images. Creating plans is off unless the server was started with PLANVORTEX_MCP_ALLOW_AI=1, because generating one spends AI credits. If create_ai_plan is not in your tool list, that is why: tell the user to add it to the env block of their MCP configuration.list_store_productsThe products of a shop connected to the organization (a WooCommerce store), to choose the ones a from_catalog AI plan writes about. Without id_integration it lists the organization's connected shops, with the id to pass back. With it, one page of that shop's products, read live: search by text rather than walking the whole catalogue, and pass next_cursor back exactly as given. Out-of-stock products come marked and cannot be chosen. A product without a price has none to show, and a price is text to repeat as is, never a number to do maths with. Connecting a shop needs a person in the PlanVortex panel.- +19 more on the listing page
Ravenpost tools 21
list_workspacesEvery workspace the credential can act in. With more than one, the other tools require a `workspaceId` rather than guessing which client you meant.list_accountsConnected accounts with their ids, platforms and status.list_postsPosts 50 at a time — newest first, or soonest first when filtered to scheduled — optionally filtered by status, with the total that matches.get_postOne post with every destination's status and permalink.preview_postRender a post as each platform will show it **without creating anything** — an interactive card in clients that support MCP Apps, and per-platform character counts everywhere else.create_postDraft, publish, schedule or queue a post across any set of accounts.update_postEdit a draft or scheduled post — resets it to draft, so pass an action to re-send it.delete_postDelete the Ravenpost copy and cancel a pending publish. Never takes a live post down from a network.schedule_postMove a post to a new time.publish_postPublish a post immediately.upload_mediaUpload an image or video from a URL or base64 (a local path too, on a development server only); images are reformatted to the platform shape you name.create_media_uploadPresigned direct upload — for large or production files, so bytes never pass through the model's context.- +9 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
PlanVortex
{
"mcpServers": {
"planvortex": {
"command": "npx",
"args": [
"-y",
"planvortex-mcp"
],
"env": {
"PLANVORTEX_CLIENT_ID": "YOUR_PLANVORTEX_CLIENT_ID_HERE",
"PLANVORTEX_CLIENT_SECRET": "YOUR_PLANVORTEX_CLIENT_SECRET_HERE",
"PLANVORTEX_ORGANIZATION_ID": "YOUR_PLANVORTEX_ORGANIZATION_ID_HERE",
"PLANVORTEX_MCP_ALLOW_AI": "YOUR_PLANVORTEX_MCP_ALLOW_AI_HERE",
"PLANVORTEX_MCP_READ_ONLY": "YOUR_PLANVORTEX_MCP_READ_ONLY_HERE",
"PLANVORTEX_MCP_AUTH_TOKEN": "YOUR_PLANVORTEX_MCP_AUTH_TOKEN_HERE",
"PLANVORTEX_MCP_UPLOAD_DIRS": "YOUR_PLANVORTEX_MCP_UPLOAD_DIRS_HERE"
}
}
}
}
Ravenpost
{
"mcpServers": {
"ravenpost-2": {
"url": "https://api.ravenpo.st/mcp"
}
}
}
Frequently asked questions
PlanVortex is categorized under Social Media and uses a local stdio subprocess. Ravenpost belongs to Social Media and uses a remote HTTP/SSE transport. Pick PlanVortex for social media work and Ravenpost for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
PlanVortex has no declared pricing — check the project's own site. Ravenpost is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add planvortex and ravenpost-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PlanVortex has a quality signal of 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Ravenpost has 53/100 (Good) with 0 views, 0 installs and 1 GitHub stars.