Post all your social media with your AI agent — 9 networks, from Claude, ChatGPT or Cursor.
to.xpost/xpost — MCP Server Model Context Protocol
The to.xpost/xpost MCP server schedules posts to nine social networks from Claude, ChatGPT, or Cursor, with visibility into each network. Its purpose is to coordinate cross-posting workflows while showing the status or details for every target.
🛠️ Key Features
Schedule posts to 9 social networks
Source from Claude, ChatGPT, or Cursor
Show each network involved
🚀 Use Cases
Cross-post content from AI tools to multiple social networks
Verify what happens on each of the nine destinations
⚡ Developer Benefits
Single workflow for posting across multiple social networks
Clear per-network visibility during scheduling
⚠️ Limitations
Designed specifically for scheduling to exactly 9 social networks
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.
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_KEY header. If you can run
commands, npx xpost wraps it and npx skills add xpost-to/xpost-agent
installs 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.