MCP for X

X's official MCP server
cannot post tweets

X shipped an official MCP server, but it is read-only. It reads and searches, it does not publish. If you want your agent to actually post, schedule, and thread on X, you need a write-capable MCP server. OpenTweet is one, and it needs no X developer account.

Get an MCP server that posts

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

Why the official one only reads

X's official MCP server exposes read operations. Publishing through X's own stack still sends you back to the X API, a developer application, OAuth, and per-use billing. That is exactly the friction agents are trying to avoid. A managed MCP server handles the account, auth, and posting for you, and exposes writing as simple tools your agent can call.

MCP servers for X, compared

X official
Open source
OpenTweet
Post tweets
No
Sometimes
Yes
Schedule and thread
No
Rarely
Yes
No X developer account
No
No, you supply your own
Yes
No self-hosting
Yes
No, you run it
Yes
X analytics tools
No
No
Yes
Maintained and managed
Yes
Varies by repo
Yes

Paste one URL. Nothing to install.

OpenTweet runs a hosted MCP server at a single URL. 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 post tweets?

No. X's official MCP server is read-only. It can search and read from X, but it cannot post, schedule, thread, or manage content. To publish to X through an MCP client you need a write-capable MCP server such as OpenTweet.

Why can the official X MCP server only read?

It is scoped to read operations. Posting through X's own stack still routes you back to the X API, a developer account, and OAuth. OpenTweet handles all of that for you and exposes writing as MCP tools.

What is the easiest MCP server that can post to X?

OpenTweet's MCP server. You connect your X account once, get a bearer key, add the server to your MCP client, and your agent can post, schedule, thread, and read analytics. No X developer account is required.

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. 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. 30 tools included.

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.

Get an MCP server that actually posts

Connect X, copy your key, and let your agent publish today.

Start your 7-day free trial