MCP for X

X has an official MCP server now.
Here is when to use it, and when not to.

XMCP is real and it can post. It also inherits everything about the X API: a developer account, OAuth app credentials, pay-per-use billing, and no scheduling. OpenTweet is the flat-fee alternative: one hosted URL, no developer account, and 30 tools that post, schedule, thread, and read analytics.

Get the flat-fee MCP server

7-day free trial. Connect in under two minutes.

What XMCP does well, and where it stops

XMCP is a clean bridge from your MCP client to the X API, with over 140 operations including posting, likes, reposts, DMs, and lists. But it is a bridge, not a product: you still apply for a developer account, manage OAuth credentials, and pay per API call, and because the X API has no scheduled-posts endpoint, everything publishes the instant your agent calls it. A managed MCP server sits one level higher. It owns the X connection for you and adds the publishing layer the raw API never had: scheduling, threads, an evergreen queue, and analytics.

MCP servers for X, compared

X official (XMCP)
Open source
OpenTweet
Post tweets
Yes
Sometimes
Yes
Schedule posts for later
No
Rarely
Yes
Thread tool built in
No
Rarely
Yes
Works without an X developer account
No
No, you supply your own
Yes
Pricing
Pay per API call
Your own API costs
Flat, from $11.99/mo
Hosted, nothing to run
Yes
No, you run it
Yes
Evergreen queue and analytics
No
No
Yes

XMCP details from the official X Developer Platform release, June 2026.

Paste one URL. Nothing to install.

OpenTweet runs a hosted MCP server at a single URL, the same setup style as XMCP. Point your client at it with your API key and your agent can post to X. No local process, no developer account, no OAuth.

# Claude Code, one command

claude mcp add --transport http opentweet \
  https://mcp.opentweet.io/mcp \
  --header "Authorization: Bearer ot_your_key"

// or add it to your MCP client config

{
  "mcpServers": {
    "opentweet": {
      "type": "streamable-http",
      "url": "https://mcp.opentweet.io/mcp",
      "headers": { "Authorization": "Bearer ot_your_key" }
    }
  }
}

See the full reference on the Twitter MCP server page.

Frequently asked questions

Can X's official MCP server (XMCP) post tweets?

Yes. XMCP exposes createPosts along with likes, reposts, deletes, DMs, and list management, over 140 operations from the X API. The catch is not capability, it is cost and setup: you need an X developer account, app credentials, and pay-per-use API billing, and there is no scheduling.

Can XMCP schedule a tweet for later?

No. The X API has no scheduled-posts endpoint, so XMCP publishes the moment your agent calls it. If you want a queue, best-times scheduling, threads, or evergreen recycling, that layer has to live somewhere else. That layer is what OpenTweet provides.

What does XMCP cost?

XMCP itself has no subscription, but every call bills against X API pay-per-use pricing, and X caps usage at 2 million post reads per month before requiring an Enterprise agreement. OpenTweet is a flat $11.99 per month with posting, scheduling, and analytics included.

When should I use XMCP instead of OpenTweet?

Use XMCP when you already have an X developer account and need the raw API surface: DMs, lists, blocking, follower management. Use OpenTweet when the job is publishing: post, schedule, thread, recycle evergreen content, and read your account analytics for a flat fee with no developer account.

Do the open-source Twitter MCP servers post?

Some do, but they are self-hosted. You run the process yourself and supply your own X developer credentials and OAuth tokens. That is more setup and maintenance than a managed server, and several have broken write paths after X's API changes.

Which MCP clients does OpenTweet work with?

Claude, Cursor, Claude Code, and any MCP-compatible client, over a hosted URL or the npm package. It exposes 30 X-specific tools for posting, scheduling, evergreen recycling, analytics, and multi-account management.

Everything you can build on X with OpenTweet

Post to X from an MCP client, code, or an AI agent. Start anywhere in the cluster.

OpenTweet vs the X API

Post, schedule, and automate X without a developer account or the $200/mo minimum.

Post to X without an API

The clean, account-safe way to post to X from your code or an AI agent.

Twitter MCP Server

Give Claude, Cursor, and OpenClaw the ability to post to X. 36 tools included.

Developer docs

Quickstart, API keys, MCP setup, and the REST reference for posting to X from code or an agent.

MCP for AI agents

Connect your AI client to X in under two minutes, no X developer account.

Developer API and keys

REST endpoints, one bearer key, and usage tracking. Build on OpenTweet.

OpenTweet for AI agents

The posting layer for autonomous agents and automations that live on X.

Build an AI Twitter persona

Give your AI agent its own X account. Setup, cadence, and the rules that keep it safe.

Skip the developer account. Keep the MCP.

Connect X, copy your key, and let your agent post, schedule, and thread for a flat fee.

Start your 7-day free trial