
Xpost
to.xpostPublished by xpost.toOfficial publisherv0.2.1Updated Nov 4, 2026
Post all your social media with your AI agent — 9 networks, from Claude, ChatGPT or Cursor.
Overview
Hosted MCP server that lets an AI assistant publish and manage posts across nine social networks from one account.
- What you can do
- List connected social accounts and what each one can carry
- Read per-account posting rules and options before composing
- Create posts that publish to one or more networks, or are held for approval
- List existing posts and check their status
- Report per-account delivery receipts and guardrail refusals
- When to use it
- Useful when you want an assistant to draft and publish social media across X, Instagram, LinkedIn, Facebook, TikTok, YouTube, Threads, Bluesky and Pinterest without switching tools, especially if you want posts held for human approval before they go out.
- Requirements
- A remote MCP endpoint at xpost.to added to your client, plus an xpost account signed in through browser OAuth. The optional skill installs via npx; a REST fallback uses an XPOST_API_KEY.
Installation
In SourceWeft
- Open Xpost in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/to.xpost%2Fxpost/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"xpost": {
"type": "http",
"url": "https://xpost.to/api/mcp"
}
}
}README
xpost for your assistant
Post all your social media with your AI agent: X, Instagram, LinkedIn, Facebook, TikTok, YouTube, Threads, Bluesky and Pinterest, from Claude, ChatGPT, Cursor, Gemini CLI or any MCP client. Want a say first? Switch on approvals and nothing goes out until a person says yes.
This repo is the open-source skill (the workflow an agent should
follow) plus the plugin manifests that install it together with the hosted
MCP server at https://xpost.to/api/mcp. You sign in once in a browser
window; nothing to paste.
You need an xpost account — the first post is free, no card: https://xpost.to/signup
Install
Any agent — as a skill
This installs the skill only. Add the MCP server in your client as below,
or let the skill's REST fallback use XPOST_API_KEY.
Claude Code — plugin (skill + MCP server)
Nothing prompts you to sign in: type /mcp, choose xpost, then
Authenticate — your browser opens on the sign-in page. Or without the plugin:
Gemini CLI — extension (skill + MCP server)
Gemini opens a browser to sign in to xpost on first use; /mcp auth xpost
signs in again.
Cursor
One click: Add xpost to Cursor
Or add it by hand in Settings → Tools & Integrations → New MCP Server:
Then npx skills add xpost-to/xpost-agent for the skill. The repo also
carries a Cursor plugin manifest (.cursor-plugin/plugin.json).
Grok Build
The repo carries a Grok Build plugin manifest (.grok-plugin/plugin.json,
skill + hosted MCP server) and its own marketplace catalog
(.grok-plugin/marketplace.json). Inside Grok Build, /marketplace browses
the catalog; from a shell, grok plugin install xpost --trust once the
source is known to it. Not yet in the official xAI index.
Muse Code (Meta)
Add the hosted server to ~/.config/muse/settings.json; Muse Code asks you
to sign in on the first tool call:
Grok, Muse and other chat assistants with no MCP settings
Paste this into the chat. The assistant sets itself up and asks you for an API key (Project → AI agent → Keys on xpost):
Set up xpost so you can post to my social accounts. The REST API is https://xpost.to/api/v1 (spec at https://xpost.to/api/v1/openapi.json), authenticated with an
Authorization: Bearer YOUR_KEYheader. If you can run commands,npx xpostwraps it andnpx skills add xpost-to/xpost-agentinstalls the workflow. Ask me for my xpost API key and set it as XPOST_API_KEY before doing anything. Start with the accounts list. Creating a post sends it, unless my project holds posts for approval — never say a post is published until the receipt says so.
ChatGPT, Claude.ai, Claude Desktop
ChatGPT: xpost is in the plugin directory — find it, add it, sign in.
Claude with the xpost plugin installed: Customize → Connectors, find
xpost, press Connect, sign in — the plugin brings the connector, signed out.
Without the plugin: Customize → Connectors → Add → custom connector, paste
https://xpost.to/api/mcp, sign in.
No MCP client at all — the CLI
The xpost package on npm is the CLI, the local MCP server (npx xpost mcp)
and the skill's fallback in one. Docs: https://xpost.to/docs/cli
What the skill teaches
- Accounts first:
list_accountsnames every destination and what it can carry. get_posting_rulesis the option catalog per account; a key that is not there cannot be used.- Creating a post sends it; a project in copilot mode holds it (
pending_approval) instead. Either is a normal outcome — say which, print the link. - A guardrail refusal names the rule. Rewrite once. Never evade.
list_postsbefore assuming a post is still waiting — the person may have rejected it with a reason.- Receipts are per account: "delivered to X, failed on Instagram: reason".
Full text: skills/xpost/SKILL.md.
Docs
- Every MCP tool: https://xpost.to/docs/mcp
- REST API (OpenAPI): https://xpost.to/api/v1/openapi.json
- Set-up guides per client: https://xpost.to/docs
Self-hosting a client against your own instance
Replace https://xpost.to with your instance in the MCP address. For the
REST fallback set XPOST_URL and XPOST_API_KEY.
License
MIT. The skill and manifests here are free to copy and adapt; xpost itself is a hosted service.
Source: README.md at commit a0e9b04
Tools
0Version history
2- v0.2.1LatestOct 14, 2026
- v0.2.0Sep 23, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts