Connect any AI agent to social media with one MCP server

Paste one address into ChatGPT, Claude, Cursor or any AI app that supports MCP, then just ask. Your agent writes, schedules and publishes posts to all top platforms through our scheduler, and every one shows up in your PostEverywhere calendar.

Start 7-day free trial Connect your agent

Get started from as little as $9 per month. $0 due today, cancel anytime.

Works with any AI agent

Used by 2,831 happy customers

PostEverywhere Agents page, connecting an AI agent with one address

Watch the full demo with sound

Connect your AI agent

Choose your AI agent and connect in seconds.

Add to Claude

Works on every Claude plan, including free. Full Claude guide

1
Add to Claude
One click from Claude’s connector directory.
2
Sign in or start your free trial
New here? Create an account and start a 7-day free trial. It’s $0 today, and a card is needed. Then allow access and you’re sent back.
3
Ask Claude
“Plan and schedule my posts for next week.”

Or paste this into any AI agent and it walks you through it:

Read https://posteverywhere.ai/SKILL.md and help me plan and schedule next week's social media posts.

Want to see the tools first? Here is everything PostEverywhere's MCP server can do.

Connect in seconds

Connect your AI agent to social media

Start your trial.: Every PostEverywhere plan includes the hosted MCP server, the REST API and the SDK.
Add the connector address to your agent.: Paste https://mcp.posteverywhere.ai into ChatGPT, Claude, Cursor or any MCP client. There is nothing to install.
Connect your social accounts.: Authorize the platforms you want your agent to publish to, across all top platforms.
Ask your agent to schedule a post.: “Schedule this to LinkedIn and X for Tuesday at 9am.” It writes, schedules and publishes for you.

Start 7-day free trial Connect any AI agent

$0 due today, cancel anytime

What your agent can do

Skills teach your agent the job. The 45 tools do the work.

See all 15 skills and prompts

Prefer to stay inside PostEverywhere? The built-in AI Assistant answers questions about your schedule and drafts posts for you to review, with nothing to set up.

Setup guides

Setup guides for every AI agent

PostEverywhere runs a hosted social media MCP server at mcp.posteverywhere.ai. Model Context Protocol (MCP) is the open standard that lets AI agents call external tools, so once it is connected, ChatGPT, Claude, Cursor or any other MCP client can schedule social media posts, generate captions (and images, on the full MCP server), retry failed posts and read analytics across all top platforms in plain language. Pick your AI agent for its setup guide, including the prerequisite each one hides behind.

Using ChatGPT? It is in ChatGPT’s Plugins

Open PostEverywhere in ChatGPT, select Connect and approve access. It works on every ChatGPT plan, including free, and there is no API key to copy.

Using Claude? It is in the connector directory

Signed-in Claude users add PostEverywhere in one click and approve access. There is no API key to copy.

Open the Claude listing

Zed or your own agent?

Use the connector address with an API key, or run the open-source server on your own machine. It works the same on every plan.

See every config

Connected already? Our step-by-step guide to scheduling posts with MCP covers time zones, per-platform captions and checking what went out. Still choosing an AI agent? Compare the best AI social media agents, see what makes a good social media MCP server, or read our State of AI Agents in Social Media report for first-party data on MCP adoption and which agents people connect. Prefer to self-host? The open-source @posteverywhere/mcp server exposes the same 45 tools.

What your agent can do

Agent prompts for scheduling social media posts

Paste any of these into your agent once it is connected. Each one maps onto real MCP tools covering scheduling, AI captions and analytics, with no glue code.

Schedule across platforms.: “Schedule this draft to LinkedIn and X for Tuesday at 9am Pacific. Optimise the caption for each platform.”
Recover failed posts.: “Retry every TikTok post that failed in the last 7 days, but skip any video over 60 seconds.”
Report on results.: “Pull my Instagram engagement metrics for last month, then suggest three posting-time changes for next month.”
Post at your best time.: “Write a post about our spring sale and schedule it on Instagram and LinkedIn at my best time.” Your agent reads your best times with get_best_times and tells you which time it picked.
Create in bulk.: “Generate three caption variants for a product-launch carousel, then bulk-schedule them across the week.”
Watch for problems.: “Subscribe to post.failed and account.disconnected events and route them to my Discord webhook.”
Repurpose long-form.: “Turn this blog post into an X Article with a cover image and schedule it for Thursday at 9am.”

Chat with your AI agent

Plan next week's posts for all my accounts and schedule one a day at 9am.

Used PostEverywhere

list_accounts8 accounts
get_platform_rulesLimits checked
generate_caption×55 captions
bulk_create_posts5 posts scheduled

Done. Five posts are scheduled for Monday to Friday at 9:00 AM, each one tailored for its platform. They are in your calendar if you want to change anything.

Mon

9:00 AM

Tue

9:00 AM

Wed

9:00 AM

Thu

9:00 AM

Fri

9:00 AM

Skills and prompts

15 agent skills and 10 ready prompts for social media

Install the PostEverywhere skills in Claude, Claude Code, ChatGPT, Gemini CLI or any agent, or open a prompt straight in Claude or ChatGPT.

Browse the skills library

Built for builders

Why agent builders pick PostEverywhere

The execution layer is the boring half of an agent. It should also be the reliable half. Your agent gets the same surface a person gets in the dashboard, through 45 MCP tools and 50 REST endpoints.

45 MCP tools, not five.: The full surface: posts, campaigns, webhooks, bulk operations, media, account health, analytics and caption generation. Your agent can reason about all of it, not just create_post.
Webhooks instead of polling.: 15 event types, so your agent reacts when something happens instead of burning tokens checking every minute.
Bulk operations, 50 posts per call.: A month of daily posts is scheduled in one request, and bulk retry by filter recovers a whole batch from a flaky platform in one call.
Pre-flight account health.: get_account_health returns can_post, token expiry and recent failures, so your agent checks before it posts and a stale token never silently stops a run.
You stay in control.: Everything your agent schedules lands in your PostEverywhere calendar, where you or your team can edit or delete it before it goes out.

Works with any AI agent

Start 7-day free trial Explore the API Read customer reviews

Agent run log

Live

08:55MCP toolget_account_healthcan_post: true
08:55MCP toolbulk_create_posts30 scheduled
09:00Webhookpost.published
09:00Webhookpost.failed
09:01MCP toolretry_failed_posts1 retried
09:02Webhookpost.published

Tool reference

Every tool your agent can use

Once connected, your agent gets 45 tools in 9 groups, the same surface as the REST API.

Posts and scheduling13
Accounts and identity9
Media6
AI captions and images2
Queue and best times2
Brand Kit1
Platform rules1
Campaigns5
Webhooks6

See all 45 tools and what each one does →

Real agent patterns

What you can build

Five agent patterns you can build on this API. For a full walkthrough, read how to build an AI social media agent; for agency setups across client workspaces, see multi-account management.

Daily content agent.: Watches your blog RSS, drafts platform-specific captions, generates an image and schedules across LinkedIn, X and Threads.
Self-healing retry agent.: Subscribes to post.failed webhooks, reads the error, decides whether to re-encode, retime or skip, then calls bulk retry. No human in the loop until something genuinely odd happens.
Engagement-aware scheduler.: Pulls the analytics summary weekly, ranks your own posting windows by engagement and rewrites next week's schedule.
Multi-client agency bot.: One agent per client, grouped with the campaigns API. get_me tells the agent which workspace it lives in, so the same code runs for client 12 or client 412.
Repurposing pipeline.: Takes a YouTube upload and drafts a LinkedIn long post, an X thread or X Article, three Instagram carousel slides and a Bluesky teaser, then schedules each one. Around 8 API calls end to end.

Daily content agent

Runs every morning

A new post goes up on your blog
RSS feed
Your agent drafts a caption for each platform
generate_caption
It generates an image to go with it
generate_image
Schedules it to LinkedIn, X and Threads
bulk_create_posts
Hears back the moment each one publishes
post.published

For developers

Your first SDK call

Building a long-running agent rather than working in an editor? The Node.js SDK wraps all 50 REST endpoints with typed resources. Webhooks, campaigns, bulk operations and account health are all on the same client. See the developers page for the full surface.

MCP server.: Use the hosted one, or run the open-source server yourself with npx -y @posteverywhere/mcp.
Node.js SDK.: A typed client for the whole REST API: npm install @posteverywhere/sdk.
Command line.: The PostEverywhere CLI is built for agents, with structured JSON output and a bundled SKILL.md for auto-discovery.

Read the docs API launch notes

schedule-post.ts

TypeScript

import PostEverywhere from '@posteverywhere/sdk';

const client = new PostEverywhere({
  apiKey: process.env.POSTEVERYWHERE_API_KEY,
});

const post = await client.posts.create({
  account_ids: [123],
  content: 'Shipping today.',
  scheduled_for: '2026-10-20T09:00:00Z',
});

Scheduledfor Tue, 20 Oct, 9:00 am UTC

Bring your own stack

Works with the agent stack you already run

If your agent can issue a Bearer-authenticated POST, it can use PostEverywhere.

Native MCP clients (zero glue code)

Add the connector address, approve access, and the tools are there.

ChatGPT
Claude Desktop
Claude Code
Cursor
Cline
Windsurf
Zed
Codex CLI

Any framework that speaks HTTP

LangChain, CrewAI, AutoGen, LlamaIndex, Vercel AI SDK, OpenClaw, or your own loop with fetch and an LLM of your choice. Either way, your agent can cross-post to every platform through one API.

LangChain
CrewAI
AutoGen
LlamaIndex
Vercel AI SDK

Prefer to run it locally?

Local config block for every MCP client

Most people should use the hosted server above, and Claude Code connects to it with one command. To run the open-source server on your own machine instead, every client follows the Model Context Protocol spec, so the same JSON works across Claude Desktop, Cursor, Cline and Windsurf. Zed nests it under context_servers, and Codex CLI uses TOML.

Claude CodeHosted server, one command

claude mcp add --transport http posteverywhere \
  https://mcp.posteverywhere.ai \
  --header "Authorization: Bearer pe_live_YOUR_KEY"

Claude DesktopFully quit and relaunch

~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
%APPDATA%\Claude\claude_desktop_config.json (Windows)

{
  "mcpServers": {
    "posteverywhere": {
      "command": "npx",
      "args": ["-y", "@posteverywhere/mcp"],
      "env": { "POSTEVERYWHERE_API_KEY": "pe_live_YOUR_KEY" }
    }
  }
}

CursorNo restart needed

~/.cursor/mcp.json

{
  "mcpServers": {
    "posteverywhere": {
      "command": "npx",
      "args": ["-y", "@posteverywhere/mcp"],
      "env": { "POSTEVERYWHERE_API_KEY": "pe_live_YOUR_KEY" }
    }
  }
}

Codex CLITOML, not JSON

~/.codex/config.toml

[mcp_servers.posteverywhere]
command = "npx"
args = ["-y", "@posteverywhere/mcp"]
env = { POSTEVERYWHERE_API_KEY = "pe_live_YOUR_KEY" }

The header must be [mcp_servers.posteverywhere] with an underscore: a mistyped header starts cleanly and loads nothing, with no error. The env line is a TOML inline table, so it needs braces and =, not JSON-style colons.

Cline, Windsurf and Zed

Cline
Same JSON block, added via the MCP Servers panel in VS Code. The panel accepts what you paste without validating it, so a server that will not start is almost always a malformed block.
Windsurf
Same JSON block, file ~/.codeium/windsurf/mcp_config.json. Windsurf reads it at startup rather than watching it, so fully restart after saving. A trailing comma makes the whole file invalid and it fails quietly.
Zed
Same shape, nested under context_servers instead of mcpServers, in ~/.config/zed/settings.json. A block left under mcpServers is ignored without any error, and Zed validates the whole settings file, so an error elsewhere in it blocks the save.

4.8on G2Used by 2,831 happy customers

What customers say

“This product just WORKS, I didn’t have any issues with it and everything went smoothly so far. For us, is a no brainer, I used to manually schedule posts in hours , now I do it in a minute. Love the Claude Connector /MCP , for us it’s worth every dollar.”
Laurentiu Cotet, RomaniaView original
“The calendar view is really nice and neatly organized. Originally there wasn’t a way to thread an X post but now there is - that was my biggest complaint but is now fixed. I was able to very easily integrate my agent into it which allows me to quickly draft and schedule dozens of posts in minutes. Super easy, great UI.”
M W, United StatesView original
“Thanks for providing this easy to use software that saves me lots of time and therefore makes me more consistent with posting. Good value.”
Lisa, AustraliaView original
★★★★★Customer
“This tool has truly made my content posting so much easier, I can't work without it. I can schedule my posts days in advance while working on other projects. Set it and forget it.”
Kim V., Content Creator
“It jusy works flawlessly. Inegrates great with Claude and makes it easy to use. Implementataion was easy. VEry happy with this tool.”
Iemke Roos, NetherlandsView original
“Most reliable no nonsense crossplatform posting app. :)”
Ang Nayyar, New ZealandView original
“I’ve found PostEverywhere very easy to use and easy to integrate into my applications.”
Jones George, United StatesView original

Read all reviews

FAQ

PostEverywhere agents FAQ

Setup, limits and how it compares. For parameters and response shapes, see the docs. Prefer to run it all from the app? See the AI social media manager inside PostEverywhere.

Can I build an AI social media agent with PostEverywhere?

Yes, that is exactly what the MCP server, REST API, and SDK exist for. Point any AI agent (Claude, Cursor, Codex, or your own LangChain or CrewAI loop) at the hosted server and it can draft, schedule, and publish across all top platforms, react to webhook events, and check account health before it posts. Connecting one takes about a minute.

Do I need an API key, or can I use OAuth?

Both. In Claude and ChatGPT you add https://mcp.posteverywhere.ai as a connector and approve access (OAuth, nothing to copy). Code clients such as Cursor, Codex and Claude Code use an API key (starts with pe_live_), which also works across the REST API and SDK.

How is this different from Zapier or n8n?

Zapier and n8n are visual workflow builders, great for "when X, do Y" plumbing. PostEverywhere is the social-media execution layer your code-level agent calls directly. No webhook-to-Zap-to-API hop, no per-task pricing. Your agent reasons in your runtime and posts via one HTTP call.

Does the MCP server work with Cursor, Cline, Windsurf, and Zed?

Yes. Anything that speaks the MCP protocol works. The config block is identical for Claude Desktop, Cursor, Cline, and Windsurf; Zed nests it under context_servers; Codex CLI uses TOML.

Why doesn't the tool show up after I add the config?

Most common cause: npx is not on PATH in the client's environment, or a JSON syntax error in the config. Claude Desktop also needs a full quit and relaunch (not just closing the window). Check the MCP logs in your client if tools are missing. For sign-in and connection failures, see why an AI agent cannot connect to PostEverywhere.

What if my agent posts the same thing twice?

Subscribe to post.published webhooks and reconcile against your agent's own memory before scheduling more. The posts list endpoint also supports filtering by content search and date range, so the agent can check for near-duplicates first.

Can I see what my AI agent did?

Yes. Every call your AI agent makes through the MCP server or the API is listed on the Logs page in PostEverywhere: the tool it called, when, how long it took, whether it worked and the error if it failed. Logs are kept for 30 days on every plan, and secrets such as API keys are redacted.

What's the rate limit?

There’s no posting cap from PostEverywhere. Each platform enforces its own limits, and very fast bursts of requests can be rate limited for a moment; the API then says when to retry. For bulk publishing, create up to 50 posts in one bulk request instead of looping.

Is the MCP server included in every PostEverywhere plan?

Yes. The hosted MCP server, the REST API and the @posteverywhere/mcp package are included on every plan, from Lite ($9/mo) to Scale ($39/mo). There’s no posting cap from PostEverywhere; platforms enforce their own limits. Every plan starts with a 7-day trial; a card is required and there is no free plan. See whether the API counts against your plan.

Should I use the hosted server or run the npm package locally?

Hosted for almost everyone: point your client at https://mcp.posteverywhere.ai with OAuth in Claude or ChatGPT, or your API key in code clients, and there is nothing to install or update. Run @posteverywhere/mcp locally when your environment cannot reach external MCP endpoints or you want to pin a version. Both expose the same 45 tools. If you would rather publish from a shell than a conversation, the CLI covers the same API from the terminal.

Is there a social media MCP server?

Yes. PostEverywhere runs a hosted social media MCP server at mcp.posteverywhere.ai with 45 tools; this page lists every tool and setup path. Model Context Protocol is the open standard that lets AI agents call external tools: an AI agent can schedule posts, manage campaigns, upload media and read analytics on your behalf, in plain language, without you touching a dashboard. Any MCP-compatible client (ChatGPT, Claude, Cursor, Codex, Cline, Windsurf, Zed) can then post across all top platforms once the server is connected. There is nothing to install with the hosted server, or you can run the open-source @posteverywhere/mcp package locally.

Can my AI agent post at my best time?

Yes. Ask it to post at your best time and it schedules for the next one, using schedule_at: "best_time" on create_post or schedule_post, then tells you which time it picked and what it is based on. The get_best_times tool lists your best times for one or more accounts or a platform, and developers can call GET /v1/best-times on the REST API. PostEverywhere bases these times on when your posts have done best; new accounts start with what works across PostEverywhere on each platform, and some platforms, like X, only get general guidance.

How do I schedule social media posts with MCP?

Connect the PostEverywhere MCP server to your agent, authorize your social accounts, then prompt the agent in plain language, for example "schedule this post to LinkedIn and X for Tuesday at 9am." The agent uses the MCP tools to publish across any of the connected platforms. The hosted server at mcp.posteverywhere.ai needs one URL (OAuth in Claude or ChatGPT, an API key in code clients), with nothing to install.

Can I schedule social media posts from Claude?

Yes. Add PostEverywhere from Claude's connector directory in one click, or add the MCP server to Claude Code with one command, then connect your accounts and ask Claude to draft and schedule posts. Claude calls PostEverywhere's MCP tools directly to publish across all top platforms, so you never leave the chat. Cursor, Codex CLI, Cline, Windsurf, and Zed work the same way.

Does the MCP server work with ChatGPT?

Yes. PostEverywhere is in ChatGPT’s Plugins: open PostEverywhere there, select Connect, sign in and approve access to your PostEverywhere account. It works on ChatGPT Free, Plus and Pro, and ChatGPT can then write and schedule posts across all top platforms. You can also add https://mcp.posteverywhere.ai by hand as a custom MCP server under Plugins on a paid ChatGPT plan.

Still have questions?

Start 7-day free trial

$0 due today, cancel anytime

Included on every paid plan from $9/mo

7-day trial with a card, $0 due today. No separate developer tier and no enterprise call: one key works for the MCP server, the REST API and the SDK.

Start 7-day free trial

See pricing