OpenTweet vs XMCP
flat fee vs pay per call
XMCP is the official X MCP server and it absolutely can post. It also inherits the X API: a developer account, a funded credit balance, per-call billing, and no scheduling. OpenTweet is the flat $11.99/mo publishing layer: one hosted URL, no developer account, and the queue, thread, evergreen, and analytics tools the raw API never had.
7-day free trial. No X developer account needed.
Two servers, two different jobs
XMCP, launched June 30, 2026, is generated straight from the X API OpenAPI spec. That makes it wide: over 140 operations covering posts, likes, reposts, DMs, search, and lists, hosted at api.x.com/mcp with a self-hosted option on GitHub. But wide is not the same as finished. Every operation maps one-to-one to a raw API call, every call bills your pay-per-use credits, and anything the X API cannot do, XMCP cannot do either. That includes the single most requested thing for a posting agent: scheduling.
OpenTweet's MCP server sits one level higher. It owns the X connection, so there is no developer account, no OAuth app, and no credit balance to fund. Its roughly 36 tools are opinionated publishing workflows: create_tweet, create_thread as one call, schedule_tweet and batch_schedule with a server-side queue, evergreen recycling, X Articles, best-time analysis, and analytics. We wrote a full breakdown of the official server in our XMCP guide and a broader look at the MCP-for-X landscape on the MCP post-to-X page.
XMCP vs OpenTweet, side by side
XMCP details from the official X Developer Platform release, June 30, 2026. Pay-per-use rates from the X API pricing update effective April 20, 2026.
What XMCP actually costs to run
XMCP has no subscription, which sounds free. It is not. Every call is metered at X API pay-per-use rates: roughly $0.015 for a plain post, $0.20 for a post containing a link, and $0.005 per read. Run the numbers for a typical posting agent that publishes 4 times a day and includes a link in half of them: 60 plain posts is about $0.90 a month, but 60 link posts is $12.00, and if the agent also reads replies and checks its own timeline a few hundred times a day, reads add tens of dollars more. A link-heavy agent, the kind that promotes a product or a blog, crosses $11.99 a month on credits alone before you have built any scheduling.
And that is the real cost gap: not the per-call cents, but the infrastructure the raw API leaves to you. Queueing posts for the right time, chaining thread replies, retrying failures, refreshing OAuth tokens, recycling your best content. OpenTweet includes all of it in one flat price, and posting through it costs the same whether your tweets contain links or not. To model your own volume against pay-per-use rates, use the X API cost calculator or read the pay-per-use pricing explainer.
Setup, compared honestly
Both servers are hosted Streamable HTTP endpoints, so neither needs a local install. The difference is what happens before you paste the URL. XMCP requires an X developer account, an app in the developer portal, API credentials, and a funded pay-per-use credit balance. OpenTweet requires connecting your X account once and copying an API key.
# 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 any MCP client config
{
"mcpServers": {
"opentweet": {
"type": "streamable-http",
"url": "https://mcp.opentweet.io/mcp",
"headers": { "Authorization": "Bearer ot_your_key" }
}
}
}Full tool list and client setup on the Twitter MCP server page, or start from the MCP overview.
Which one is right for you
Pick XMCP if
- You need the full read API: search, timelines, or the firehose
- Your agent manages DMs, lists, likes, or blocking
- You already have a developer account and funded credits
- You want operations OpenTweet does not expose, and per-call billing fits your volume
Pick OpenTweet if
- Publishing is the job: post, schedule, thread, recycle
- You do not have, or do not want, an X developer account
- You want one predictable bill instead of metered credits
- You want evergreen, articles, best times, and analytics without building them
They are not exclusive. Plenty of agents use XMCP for reading and OpenTweet for publishing, side by side in the same client.
Frequently asked questions
What is XMCP?
XMCP is X's official MCP server, launched June 30, 2026. It is generated from the X API OpenAPI spec and exposes more than 140 operations, including posting, likes, reposts, DMs, search, and list management. The hosted version runs at api.x.com/mcp over Streamable HTTP, and there is an open-source version you can self-host.
Can XMCP post tweets?
Yes. XMCP can create posts, not just read data. The difference is not capability, it is cost and setup: you need an X developer account with a funded credit balance, every call bills X API pay-per-use rates, and there is no scheduling because the X API has no scheduled-posts endpoint.
How much does XMCP cost to use?
XMCP itself has no subscription, but every call it makes bills your X API pay-per-use credits: roughly $0.015 per post, $0.20 per post that contains a link, and $0.005 per read. An agent posting a few link posts a day plus reading replies can pass $11.99 a month on API credits alone, which is OpenTweet's entire flat Pro price.
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. To get a queue you would keep the agent process alive until publish time or build your own scheduler. OpenTweet's schedule_tweet and batch_schedule tools store the post and publish it server-side at the right time.
When is XMCP the better choice?
When you need the raw X API surface. XMCP covers DMs, full search, likes, reposts, blocking, and list management, none of which OpenTweet exposes. If you already have a developer account and your agent needs to read the firehose or manage DMs, XMCP is the right tool, and you can run both servers side by side.
What does OpenTweet's MCP server include that XMCP does not?
Scheduling, threads as a single create_thread call, batch scheduling, an evergreen recycling queue, long-form X Articles drafting and publishing, best-time analysis, and posting analytics. It also removes the developer account entirely: OpenTweet manages the X OAuth tokens and refresh for you, and pricing is a flat $11.99/month.
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.
XMCP vs OpenTweet
X's official MCP server bills per API call and cannot schedule. Compare it with the flat-fee hosted MCP.
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