Ayrshare's MCP server: there are two, and one of them cannot post

Ayrshare has two MCP servers and only one of them can publish: the Action MCP, which needs an API plan from $149/month. If you connect the other one, the Documentation MCP, nothing fails: your agent reads API documentation while you wait for a post that never goes out. On PlanVortex the same job is done by a single server, starting on the free plan.

All of it verified on September 15, 2026 against Ayrshare's own documentation and PlanVortex's production code.

How do Ayrshare's two servers differ?

The Documentation MCP searches their docs and the Action MCP drives the API:

	Documentation MCP	Action MCP
What it does	Searches Ayrshare's API docs	Drives the Ayrshare API
Can it publish?	No	Yes
Tools	Documentation search	27, across publishing, analytics, history, comments, DMs and profiles
Auth	None	Bearer token
Price	Free	Needs an API plan, from $149/month

Ayrshare's own docs put it this way: "This is the read-only Documentation MCP (it searches Ayrshare's API docs). To let an AI agent drive the Ayrshare API, see the MCP Server (Action MCP)."

The Documentation MCP is a good idea: a coding agent working against real API docs writes an integration that compiles rather than one that invents endpoints. But it does not publish, which is what you wanted when you asked for a post to go out on Thursday.

There are also community-built Ayrshare MCP servers on the registries, some with a much larger tool count, and they are unofficial. Whether that matters is your call, but it is your token they are holding.

How much does the Action MCP cost?

At least $149 a month. It is a second door onto the Ayrshare API, so it inherits that API's price: Premium, $149/month, which is Ayrshare's cheapest plan. There is no free tier and no permanent free key.

Against PlanVortex:

	Cheapest plan that can publish from an agent
Ayrshare	$149/month
PlanVortex	€0/month

PlanVortex's MCP server authenticates with the client_id and client_secret of an app, and every plan has apps, the free one included: one on free, two on basic, five on pro, up to ten on custom. What scales with the plan is how many separate apps you get and how fast you can call, not whether an agent can publish at all.

npx -y planvortex-mcp

Those are the same credentials the Node and Python libraries use. It is listed in the official MCP registry and installs as a one-command npx, with a .mcpb bundle for Claude Desktop if you would rather not have Node on the machine.

Which tools does PlanVortex's MCP server have?

Thirty-one, and none of them deletes anything. Grouped by what you would ask for:

• Publishing: create_publication, update_publication, retry_publication, upload_media, get_publication, list_publications, list_destinations
• The comment inbox: list_comments, get_comment_thread, reply_to_comment, hide_comment, mark_comment_read
• Private messages: list_conversations, list_messages, send_message, get_unread_counts
• Accounts and setup: list_organizations, list_accounts, create_connect_link, get_plan_use, get_social_capabilities, get_social_limits
• Numbers: get_dashboard_summary, get_account_metrics, get_publication_stats, get_top_publications
• AI planning: get_planner_templates, list_store_products, list_ai_plans, get_ai_plan, get_ai_plan_results

A thirty-second, create_ai_plan, generates a whole week of posts and spends AI credits, so it stays off until you start the server with PLANVORTEX_MCP_ALLOW_AI=1. It is opt-in on purpose: an agent that spends credits where nobody can see it ends up as a support ticket.

The missing delete tool is also on purpose. No tool removes a post, an account, a contact or a comment. An agent that misreads an instruction can publish something you have to retract, but it cannot erase a client's inbox. Deletions happen in the dashboard, by a person.

On tool count, 27 against 31, the two servers are close. What separates them is the price.

What decides between Ayrshare and PlanVortex?

Whose accounts you are publishing to. Both servers publish and both read analytics.

Ayrshare's API is built to publish on behalf of your users, and it is good at it: that is what user profiles are for. What you are paying $149/month for is the floor to find out whether it fits.

PlanVortex separates clients, organizations and accounts in the data model rather than bolting a client_id onto a single-company schema, and the account connection itself is an API call: create_connect_link returns a link your user opens to authorize their own Instagram, on your screens, under your brand. So an agent can take a customer's onboarding from start to finish, as well as post to accounts that are already connected.

What does Ayrshare do better?

The Documentation MCP, which has no equivalent here. If you want an agent that writes your integration correctly, theirs works; ours is an action server only.

Which one should an assistant use to publish?

• Connect the Action MCP, not the Documentation one. Mixing them up is the easiest way to lose an afternoon with Ayrshare.
• Ayrshare's floor to publish from an agent is $149/month. PlanVortex's is €0, on the free plan, with the API and an app included and no card.
• Tool counts are level (27 vs 28). What decides it is whether you need to connect your customers' accounts from your own product, and whether you want the comment inbox and DMs in the same server.
• If you want an agent that writes your integration rather than one that publishes, their Documentation MCP is the tool, and we have nothing like it.

PlanVortex's MCP server is documented at planvortex.com/en/agents, and the npx -y planvortex-mcp above is the whole install.