Best social media MCP servers and AI-agent tools (2026)

If you want an AI agent to post to social media in 2026, you have plenty of MCP servers to choose from. As of October 2026, Buffer, Hootsuite, Metricool and Postiz all run official MCP servers, and Mixpost ships one in its paid Pro license. pendpost is the local-first, MIT-licensed option, built around a human approval gate.

Picking between them comes down to two questions. Where should the tokens that can publish as you live? And what happens between the agent’s draft and the public post? Each tool below answers those differently, and a few of them will suit you better than pendpost does.

What is a social media MCP server?

A social media MCP server is a program that exposes posting and scheduling as tools an AI assistant can call. The Model Context Protocol (MCP) is the open standard behind it. “Post this to LinkedIn on Thursday” becomes a tool call the assistant actually runs, so you stop copy-pasting between a chat window and a dashboard.

Platform count matters less than you might think. What separates these servers is where they run (your machine or a vendor’s cloud), who holds your credentials, the license, and whether anything stops the agent from publishing a post nobody approved.

Which MCP servers can post to social media?

Most of the big schedulers now run a hosted MCP server, and two open-source schedulers ship one you can host yourself. Everything below was checked against the vendors’ own docs and pricing pages in October 2026.

Hosted servers from the big schedulers

• Buffer (proprietary, hosted). A remote server at mcp.buffer.com/mcp that reads your channels, queue and drafts, schedules and edits posts, and pulls post analytics. Every plan comes with API keys, the free one included (one key on Free). Best if you already use Buffer and want an agent on top. See Buffer alternatives.
• Hootsuite (proprietary, hosted). Four product servers: Perch drafts and schedules posts, Nest handles the inbox, Lumen covers listening, and Parliament covers employee advocacy. Each needs an active account with access to that product. Best for larger teams already on Hootsuite. See free Hootsuite alternatives.
• Metricool (proprietary, hosted). A server at ai.metricool.com/mcp that works on every plan, Free included, within your plan’s limits. It reads analytics and reports, creates and publishes posts, and touches ad campaigns and the inbox. Best when analytics are the point. See Metricool alternatives.
• API-first hosted services. Zernio runs a hosted server at mcp.zernio.com/mcp and is listed in the official MCP Registry. Eclincher launched a remote server that publishes, schedules and works the inbox across eight networks. Outstand offers one too. All of them run in the vendor’s cloud and act on your accounts once you connect them.

Open-source and self-hosted servers

• pendpost (MIT, local-first). Runs on your own machine, binds 127.0.0.1, keeps your keys in your own .env, and never phones home. An agent drafts and schedules behind a human approval gate you control, with anti-ban circuit breakers and a caption brand-lint. Covers Instagram, Facebook, LinkedIn, YouTube, X, Telegram, Discord, Mastodon, and Nostr, plus long-form blogs on WordPress and Ghost, with Reddit, Pinterest, TikTok, and Google Business Profile in beta. Best when you want agent help and insist on human sign-off and data ownership. See the MCP server page and the MCP setup docs.
• Postiz (AGPL-3.0). A broad open-source scheduler whose network list includes Instagram, TikTok, Threads, Bluesky and Mastodon. Its MCP server starts as part of the Postiz backend, so it works on Postiz Cloud and on self-hosted installs alike, and it can also generate images and video and clip long YouTube videos into drafts. Best when you want wide platform coverage and a mature dashboard. See Postiz alternatives or the head-to-head pendpost vs Postiz.
• Mixpost (MIT Lite, paid Pro, self-hosted). The free Lite edition is MIT and publishes to Facebook Pages, X and Mastodon. The paid Pro license adds Instagram, LinkedIn, YouTube, TikTok, Threads, Bluesky and more, plus an approval flow and the MCP server. Best for a team that wants a self-hosted dashboard and is happy to buy Pro.

You will also find community servers for tools without an official one, Typefully and Sprout Social among them. They can work well; check who maintains them before you hand one your tokens.

Where does each tool put the approval step?

The approval step is the one thing between a bad agent draft and your followers, and only some tools make it a state that blocks publishing. Here is where each one keeps it, from the vendors’ own pricing pages and docs in October 2026:

Tool	Approval that blocks publishing	Where it lives
pendpost	Yes, on by default	Free core; an agent can never approve its own post
Buffer	Yes	Team plan (“content approval workflows”)
Hootsuite	Yes	Advanced and Enterprise plans
Metricool	Yes	Advanced and Custom plans (“post approval system”)
Mixpost	Yes	Paid Pro license (“approval flow”)
Postiz	No approved state	Drafts plus a public preview link for client comments

Postiz is upfront about that last row. Its docs say approval “is a conversation, not a state”: you save posts as drafts, send a preview link, read the comments, and move the post to scheduled yourself. That works fine for a human team. With an agent holding a scheduling tool, I would want something the agent cannot skip.

Your MCP client adds one more layer. Claude and most other clients ask before running a tool, and the MCP spec says a human should be able to deny tool calls. Keep those prompts on. They confirm a single call in a single chat, though, and they do nothing about a post that is already sitting in a queue.

Plans change, so check the vendor’s pricing page before you rely on any row above.

Hosted or local: which should you pick?

Pick a hosted server if zero setup matters more to you than data ownership, you want a team login, and you are fine with a vendor holding your social credentials. Buffer, Hootsuite and Metricool are all solid choices there.

Pick a local-first server like pendpost if you want your tokens on your own machine, a tool that never phones home, a permissive license you can build on, and a human approval step between the agent and the public. The trade-off is real: you run a process yourself (npx pendpost or docker compose up), and you connect each platform with your own API credentials. Self-hosted Postiz and Mixpost sit in between. Your own server holds the keys, but you run and update a full web app yourself.

How does pendpost differ?

In pendpost the approval gate is the core of the design. Every post is fail-closed: the agent can draft and schedule all day, and nothing goes live until someone approves it. By default that someone is you. Auto-approve exists, as an opt-in only the owner can grant and revoke. The approval and circuit breaker docs spell out the exact rules.

It also watches for trouble. When a platform blocks an action, a circuit breaker halts that lane until you clear it, so an agent does not keep pushing into an account the platform has already flagged.

If that fits how you want to work, read how to let an AI agent post to social media safely, see the AI social use case, or try it in mock mode with PENDPOST_MODE=mock PENDPOST_ROOT=/tmp/pendpost-demo npx pendpost (mock mode only starts with a data folder inside your temp directory). You need no credentials for that.

Frequently asked questions

Sources

• Buffer developer docs: MCP server
• Buffer pricing (API keys per plan, approval workflows)
• Hootsuite MCP servers
• Hootsuite plans
• Metricool help: how to connect Metricool's MCP
• Metricool pricing
• Postiz docs: MCP
• Postiz docs: approvals
• Postiz repository and license
• Mixpost pricing and editions
• Mixpost Lite repository (MIT)
• Zernio
• Eclincher MCP server
• Model Context Protocol specification: tools

All postsRSS feedpendpost home