What posterly MCP server does
The posterly MCP server exposes social publishing and management functions through the Model Context Protocol. It can connect an assistant to accounts on Instagram, Facebook, TikTok, X, LinkedIn, YouTube, Pinterest, Threads, Google Business, Telegram, Bluesky, Discord, Slack, Mastodon, Dev.to, Hashnode, WordPress, and Lemmy.
Available operations include listing accounts and platforms, checking posts before publication, creating scheduled posts, updating existing posts, finding available publishing slots, and submitting batches of up to 25 posts. The catalog also includes media handling, caption and image generation, analytics, comments, direct messages, Google Business reviews, profile audits, API keys, webhooks, workspace members, publishing pauses, and billing functions. The exact catalog is maintained on poster.ly/mcp.
How it works
You can use the hosted endpoint at https://www.poster.ly/api/mcp or start the npm package with npx -y posterly-mcp-server@latest. The hosted service uses JSON-RPC 2.0 over one HTTPS POST and returns a JSON response; it does not provide an SSE stream. Authentication is handled through OAuth in supported connectors or an Authorization: Bearer header containing a Posterly API key.
Local operation uses standard MCP configuration with the posterly-mcp-server package and POSTERLY_API_KEY. The local catalog includes signup tools that are not available on the hosted endpoint. A key is needed for authenticated tools, while some local signup and account-status actions can begin without one.
Write operations include confirmation safeguards. create_post requires confirm: true, while comment replies, direct messages, Google review replies, and similar actions first return a preview that must be submitted again with the preview identifier. Hosted create-post calls are limited to 100 requests per hour per key.
Setup and configuration
For local use, the basic MCP entry runs npx -y posterly-mcp-server@latest and passes POSTERLY_API_KEY in its environment. Node.js 20 or newer is required. The package is intended to be installed through the npx configuration; the GitHub repository is a read-only source mirror rather than a separate installation path.
For hosted use, configure https://www.poster.ly/api/mcp using the www hostname. Claude and ChatGPT custom connectors use OAuth. Clients that accept HTTP headers can use a bearer key instead. Cursor supports either hosted HTTP or local stdio, while Claude Code and Codex provide commands for both approaches. Windsurf, Cline, Continue, and Zed can use the same local JSON configuration shape.
A Posterly plan with API and MCP access is required for authenticated tools. Pricing, key limits, and subscription details depend on the selected plan.
Tools and capabilities
The tool groups cover core account, posting, media, schedule, analytics, and support functions; creative generation; inbox actions; Google Business operations; administration; and billing. Representative tools include list_accounts, validate_post, create_post, create_posts_batch, list_posts, upload_media, generate_captions, generate_image, list_analytics, list_comments, manage_comment, list_google_business_reviews, and manage_google_business_review.
For clients that cannot send file bytes, media can be staged through a browser-accessible media drop. Clients that can upload bytes can request a signed upload URL. Small images can use the media upload tool.
Limitations and notes
Analytics currently covers Instagram, X, Facebook Pages, LinkedIn, Google Business Profile, Pinterest, YouTube, and Threads. ChatGPT web uses the hosted endpoint only; write actions require Business, Enterprise, or Edu, while Pro custom MCP is limited to read and fetch operations. ChatGPT custom MCP is web-only.
The posterly MCP server does not use SSE for its v1 hosted transport. Hosted chat attachments do not reach the service directly. On ChatGPT web, Claude.ai, and Gemini web, media workflows use a generated drop link; local-capable clients such as Cursor, Claude Code, and Codex can use signed uploads.