What is an MCP server for social media?

MCP — the Model Context Protocol — is the standard way to hand an AI assistant a set of tools. A social media MCP server is one that gives it posting tools: connect it and your assistant can write, schedule and publish to your accounts, and read back what happened.

How do I add the xpost MCP server to Claude or ChatGPT?

In Claude, Cursor or Claude Code, paste https://xpost.to/api/mcp wherever the client asks for a connector or an MCP server, then sign in when your browser opens. In ChatGPT, xpost is in the plugin directory — add it there and sign in. There is no key to copy and no file to edit. The per-client steps are on the pages for Claude, ChatGPT, Cursor, Claude Code and n8n.

Is it a hosted server or do I run it myself?

Hosted, at the address above, over Streamable HTTP. There is also a local stdio server for clients that need one — the connector reference covers it.

Can an agent publish without me?

It can, and you are told every time: the post is mailed to you, before it goes out or the moment it has. Switch approvals on and anything an agent creates waits in your queue instead. Approval is a human action — no key, tool or prompt can skip it.

Which networks can it post to?

X, Instagram, LinkedIn, TikTok, YouTube, Facebook, Threads, Bluesky and Pinterest — the same nine as the dashboard, with the same per-network shapes, limits and previews.

Does the MCP server cost extra?

No. It is included in every plan, along with the REST API and all 17 tools. You pay for the accounts you connect; posts are unlimited.

MCP

The social media MCP server.

One address, added to any assistant that speaks the Model Context Protocol. It gets 17 tools for posting to 9 networks — and no way to publish anything a person is not told about.

Server addresshttps://xpost.to/api/mcpPaste this wherever your client asks for an MCP server or a connector. It signs you in through your browser; there is no key to copy.

What it is

MCP is how an assistant is given tools. This is the one that posts.

A hosted server, not a package

Streamable HTTP at one address. Nothing to install, nothing to run, and it is the same server for every client.

The same API as the dashboard

Every tool goes through the public API, so approvals, key scopes and rate limits apply exactly as they do on screen.

In every plan

The server, all 17 tools and the REST API are included in every plan. No usage meter and no per-call fee.

Adding it to a client

Three steps, about two minutes, and the same three in every client.

1
Paste the address
Add the server address above wherever your client keeps its MCP servers or connectors.
2
Sign in once
Your browser opens the xpost sign-in page. Log in and the connection is made — no keys, no config file to edit. End it any time from Settings.
3
Ask for a post
Say what you want, for which accounts and when. The post goes out at the time you set, lands in your inbox, and each account comes back with its own receipt.

Set it up in

The 17 tools

What a connected client can do, in plain words. Each name opens its own reference — the arguments it takes and what it changes.

create_postWrite a post for one or more accounts, now or at a time you choose.
update_postChange the text, pictures or time of a post that has not gone out yet.
delete_postRemove a post that has not been published.
bulk_postCreate many posts at once from a list.
list_postsSee your posts, filtered by status, account or date.
list_accountsSee which accounts are connected and healthy.
get_posting_rulesAsk what each account accepts — lengths, surfaces, options — before writing.
get_projectRead the project's name, time zone and settings.
get_delivery_receiptSee exactly where a post landed, account by account.
retry_deliverySend one account's delivery again.
take_down_postRemove a published post from the networks.
list_connection_issuesFind accounts that need a fresh sign-in.
get_insightsRead reach, likes and comments for a period.
get_top_postsSee which posts did best.
get_post_metricsRead the numbers for one post.
get_best_timesFind the hours your audience reads.
upload_mediaAdd a picture or video from a web address.

The full connector reference

The networks it reaches

One tool call, the right shape for each of them, and a receipt per account.

Safe by design

You see every agent post

Anything an assistant creates lands in your inbox, with the post in the message. Switch approvals on and it waits in your queue until you say so.

It tries again, and tells you

A delivery that fails is retried on its own, and if it still can't go, you get an email saying which account and why.

Every post gets a receipt

Each account is delivered on its own and recorded on its own. You can always see what happened.

No key can approve

Approval is a human action in the dashboard or the chat. No key, tool or prompt can skip it.

FAQ

Questions people ask

MCP — the Model Context Protocol — is the standard way to hand an AI assistant a set of tools. A social media MCP server is one that gives it posting tools: connect it and your assistant can write, schedule and publish to your accounts, and read back what happened.