The MCP Server for Social Media

Drop the Posta MCP server into Claude Desktop, Cursor, Windsurf, VS Code, Zed — or any agent that speaks Model Context Protocol — and post to LinkedIn, TikTok, Instagram, YouTube, Pinterest, Facebook, Bluesky, and Threads with a single tool call. Open source, free, on npm.

Install in 30 seconds

Add the Posta MCP server to your client's MCP config (Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, Zed all read the same mcpServers shape). Set your POSTA_API_TOKEN, restart the client, and the Posta tools appear in the tool list.

// claude_desktop_config.json (or your client's MCP config)
{
  "mcpServers": {
    "posta": {
      "command": "npx",
      "args": ["-y", "posta-mcp"],
      "env": { "POSTA_API_TOKEN": "your_token_here" }
    }
  }
}

Compatible clients

Claude Desktop
Anthropic's reference MCP client. Add Posta and ask Claude to draft and schedule posts in plain English.
Claude Code
Bring Posta tools to the terminal alongside the dedicated Claude Code skill.
Cursor & Windsurf
Make Posta a tool your IDE agent can reach for while it edits your post-generation code.
VS Code & Zed
Any editor with an MCP extension picks up the same server config — no per-editor adapter.
Custom agents
Build on the MCP TypeScript, Python, or Rust SDK and Posta's tools work the same way.
Multi-agent frameworks
LangChain, CrewAI, OpenAI Agents SDK — all interoperate with MCP servers through their MCP tool adapters.

Tools the server exposes

createPost
Create a draft, scheduled, or immediate post on one or many connected accounts.
schedulePost
Move a draft to a future timestamp. Time-zone safe.
listAccounts
Enumerate connected social accounts so the agent can pick targets.
getPostStatus
Check whether a post is queued, processing, posted, or failed.
listMedia / uploadMedia
Browse the media library or push a new asset; Posta handles per-platform variants.
listPosts
Inspect drafts, scheduled, and posted history — useful for "what did I post last week" prompts.

Example prompts

Once the server is wired up, the agent picks the right tool from the prompt — no API knowledge required.

"Draft a LinkedIn post announcing v2.1 of our SDK and schedule it for Tuesday 9am CET."

"Repost the top performer from last week to Bluesky and Threads — keep the caption short."

"List my scheduled posts for next week and tell me which ones are missing images."

Why MCP for social media?

Typed tools, no docs in the prompt
MCP gives the model machine-readable schemas. The agent learns the right call by introspection — no brittle prompt-engineered API reference.
One transport, many clients
Same server config works in Claude Desktop, Cursor, Windsurf — switch clients without rebuilding the integration.
Streamed results
Tool responses stream back to the model, so long-running operations (uploads, scheduling) don't block.
Token-efficient
Tool definitions live in the client, not in every prompt — fewer tokens, faster turns.

Frequently asked questions

What is an MCP server for social media?
An MCP (Model Context Protocol) server exposes a set of typed tools to any compatible AI client. The Posta MCP server exposes tools like createPost, schedulePost, listAccounts, and uploadMedia, so an MCP client (Claude Desktop, Cursor, Windsurf, VS Code, Zed) can post to eight social networks as native tool calls.
Which MCP clients does Posta work with?
Any client that implements MCP — Claude Desktop, Claude Code, Cursor, Windsurf, VS Code with MCP extensions, Zed, and custom agents built on the MCP SDK in TypeScript, Python, or Rust.
How do I install the Posta MCP server?
Add the Posta MCP server to your client's MCP config (Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, Zed all read the same mcpServers JSON shape). Set POSTA_API_TOKEN in the env block, restart the client, and the Posta tools appear in the tool list. Source on GitHub; package on npm.
Is the MCP server free?
Yes. The posta-mcp package is open source and free on npm and GitHub. You only pay for the Posta plan that covers your usage volume, with a 14-day free trial to start.
Why MCP instead of the REST API?
MCP tools come with typed schemas the model can introspect, so the agent picks the right call without API docs in the prompt. For non-LLM automation pipelines, the REST API is the better fit. Many users wire up both — MCP for interactive agents, REST for the n8n flows.

Wire Posta into your agent today

MCP server, Claude Code skill, n8n node, REST API. 14-day free trial, no credit card.