Twitter MCP Servers: Connect Claude, ChatGPT and Agents to X

A Twitter MCP server is a small program that lets an AI assistant such as Claude, Cursor or an OpenClaw agent call X as a set of tools. It can search posts and look up users, and some servers can also post, like or DM. X now runs an official one, hosted at

This post covers what the official X MCP server can and cannot do, nine community options we checked on GitHub in October 2026, how to connect one to Claude, and the account risk that comes with each.

What a Twitter MCP server actually does

MCP (Model Context Protocol) is a standard way to give an AI model a list of tools. An X MCP server turns a request like "search for posts about our launch" into an API call and passes the result back to the model.

Three questions decide which server you want:

1. Does it read, write, or both? Many servers only read. A smaller group can post, like, follow and send DMs.
2. Does it use the official API or a session? Official means your own X developer app with pay-per-use billing. Session means the server logs in as you with cookies, a password or a real browser.
3. Who pays per call? On the official API, every read is billed, and an agent left running on its own reads a lot. One developer on r/openclaw, u/NHI10, gave an agent a pay-per-use key and reported: "After ~10 minutes and ~1000 tweets from one user, $5 was gone".

The official option: X's hosted MCP and xmcp

X launched an MCP server for AI models on February 6, 2026, along with pay-per-use pricing (X changelog). There are now three official pieces (X MCP docs):

• X MCP (hosted) at
  https://api.x.com/mcp
  . Tools cover fetching posts and their likers, reposters and quoters, full-archive and user search, news search, user lookups and timelines, bookmarks, trends, and drafting and publishing Articles. You connect through
  xurl mcp
  , a local bridge that handles the OAuth 2.0 login once and refreshes tokens for you. A simpler app-only route takes a Bearer token in a header, but it is read-only and can't act as you.
• xmcp (xdevplatform/xmcp), an open-source server you run locally. It exposes X API endpoints from the OpenAPI spec as tools, and an allowlist lets you expose only the ones you need. X's docs say it covers 200+ endpoints. 862 stars, last commit April 9, 2026.
• Docs MCP at
  https://docs.x.com/mcp
  , which lets an assistant search X's developer documentation.

It is still the official API, though. Calls are billed at pay-per-use rates ($0.005 per post read, $0.015 per post created), and self-serve rules apply. Since April 2026, following, likes and quote-posts aren't available on self-serve tiers. Since February 2026, programmatic replies are allowed only when the original author mentioned or quoted your account. The hosted server's documented write tools cover bookmarks and Articles, so it works as a research tool rather than an outreach tool.

Community Twitter MCP servers, checked October 2026

Stars and last-commit dates were checked on GitHub on October 13, 2026.

Some things don't fit in the table:

• EnesCinr/twitter-mcp is the simplest server built on the official API. It has two tools,
  post_tweet
  and
  search_tweets
  , and hasn't been updated since July 2025, so test it against the current API before you rely on it.
• rafaljanicki/x-twitter-mcp-server says it uses official API keys "to minimize the risk of account suspensions". It also lists favoriting and follower management, which X no longer offers on self-serve tiers. Expect those tools to fail on a pay-per-use app.
• x-use is the most careful of the session-based servers. Messages, follows and new threads are staged as drafts that need your approval, and it tracks a budget for each account. It still runs on your logged-in browser session rather than the API.
• XActions advertises "No API keys. No monthly fees." and about 150 MCP tools, and says logging in adds search, followers and DMs. That's the session route in its most complete form.
• mcp-twikit depends on twikit, which developers describe as stale. u/Icy-Care-353 on r/webdev found it "not maintained anymore and full of bugs".

Official API vs session cookies: the trade you are making

The decision that matters is the split in that table.

The official API servers (X MCP, xmcp, EnesCinr, rafaljanicki, x-research-skill) stay inside X's rules. You pay per call and accept the self-serve limits, which rule out follows, likes and unsolicited replies.

The session servers (XActions, x-use, mcp-twikit) cost nothing per call and can do anything the X website can. They also sit outside X's Terms of Service, which say you may not access X "other than through our currently available, published interfaces" and that "crawling or scraping the Services in any form, for any purpose without our prior written consent is expressly prohibited" (X Terms, effective October 9, 2026).

In practice, X enforces this at the account level. When someone asked on r/openclaw whether OpenClaw can post on X, u/bodobeers2 said they ran an agent that posted once a day with no trouble: "The second I tried an at mention, it suspended the accounts." In the same thread, u/redeaglemuffin answered: "I don't recommend you to use automation to post. Only to read." And in another r/openclaw thread, u/anthonyg45157 summed up the community view: "Skirting X API can definitely get you banned but using browser automation is the way".

Key insight: Reading through an MCP server is low risk on either route. Writing, especially replies and mentions, is where accounts get suspended.

How to connect an X MCP server to Claude

This is the official route, taken from X's own setup guide. Start by creating an app in the console with OAuth 2.0 enabled, then register

{
  "mcpServers": {
    "xapi": {
      "command": "npx",
      "args": ["-y", "@xdevplatform/xurl", "mcp", "https://api.x.com/mcp"],
      "env": { "CLIENT_ID": "YOUR_X_APP_CLIENT_ID", "CLIENT_SECRET": "YOUR_X_APP_CLIENT_SECRET" }
    }
  }
}

For Claude Code, the same server takes one command:

claude mcp add xapi -e CLIENT_ID=YOUR_X_APP_CLIENT_ID -e CLIENT_SECRET=YOUR_X_APP_CLIENT_SECRET \
  -- npx -y @xdevplatform/xurl mcp https://api.x.com/mcp

The first time you use it, your browser opens for a one-time X login. X's docs warn that the login authorizes "whichever X account is logged in when the browser opens", so switch to the right account before you start. If you see

X's guide also covers Cursor, VS Code and Grok Build. ChatGPT isn't in it. If you want X inside ChatGPT, check whether your ChatGPT plan lets you add a remote MCP server with a custom header, because X's hosted server accepts an app-only Bearer token that way.

Set a spending limit in the X console before you let an agent run. Agents page through results eagerly.

OpenClaw and Twitter

Most people searching "OpenClaw twitter" are trying to wire X into an OpenClaw agent. OpenClaw can load MCP servers and skills, so the options above all apply. There's also a third: give the agent browser control over a logged-in Chrome. One builder explained in a detailed write-up on r/openclaw that Cloudflare blocked twscrape "almost immediately, even with rotating sessions" before a browser session worked.

The most useful answer in the posting thread came from u/Nanesses: "most people you're seeing are not fully automated, it's usually hybrid: AI drafts + human oversight + scheduled posting". Copy that pattern.

The case against letting an agent touch X at all

The strongest objection is that an LLM running a social account will eventually do something you would not have done, and X is already watching for that. X's February 2026 changelog entry restricting programmatic replies is titled "Addressing LLM-generated spam". There is even an r/openclaw thread titled "use Openclaw but twitter account was quickly banned".

For open-ended engagement, the objection is mostly right. Auto-replying, auto-mentioning and auto-following strangers are jobs you should not hand an agent on an account you care about. It holds up less well against narrow, paced, human-approved work: research, drafting, and sending messages you have reviewed, at a rate a person could plausibly keep up. Work like that behaves like a workflow you supervise, and a spam bot does none of it.

Acting on X from an agent without an MCP server

XAutoDM does not have an MCP server. It has a REST API and a public Claude skill, and for outreach that is often the simpler setup.

The skill, cold-dm-claude-skill, installs with one command and is invoked as

npx skills add whatsuppiyush/cold-dm-claude-skill
export XAUTODM_API_KEY="xdm_live_..."   # or an xdm_test_ key to dry-run with no sends

With it, Claude Code (or any agent that loads Anthropic-style skills) finds followers and engagers who can receive DMs, drafts a first message from each person's real profile, and runs a paced campaign through the API. It estimates the credit cost and asks before every spend. It refuses mass blasts and never touches X directly: every action goes through the API with your own key.

Underneath sits the XAutoDM API, built for writes across many connected X accounts. DMs cost 10 credits each; follows, likes, retweets and posts cost 5 credits each, and reads cost 5. Plans start at $49 a month for 10 connected accounts and 59,000 credits, and new signups get 200 one-time credits. If you only need to bulk-read tweets, a read-only API is cheaper. The same endpoints work from automation tools, which our n8n, Zapier and Make guide walks through.

One caveat. The API acts through connected X account sessions, not X's official API, so under X's terms it sits in the same category as the session servers above. What it adds is the guardrails an agent lacks on its own: per-account pacing within safe daily limits, idempotent sends so a retry never double-messages, and a person approving the campaign. For the cost side of the official route, see our X API pricing breakdown.

Pick your next step by job. For research, connect X's official MCP server to Claude and set a spending limit. For outreach, install the x-outreach skill with a test key, run one dry campaign, and read every draft before anything goes live.

Frequently asked questions

Is there an official X MCP server?

Yes. X hosts one at api.x.com/mcp, which you reach through its open-source xurl bridge. There is also an open-source local server, xmcp, that exposes X API endpoints as MCP tools. Both run on your own X developer app and bill calls at normal pay-per-use rates, for example $0.005 per post read.

Can Claude post to Twitter through MCP?

Yes, if the server has write tools and you give it a user token. X's hosted MCP is mostly about reading, bookmarks and Articles. Community servers such as EnesCinr/twitter-mcp add a post_tweet tool that uses official API keys. Each post costs $0.015 on pay-per-use, or $0.20 if it contains a link.

Will an X MCP server get my account banned?

Servers that call the official API with your own keys stay inside X's terms, though automated replies and mentions are restricted. Servers that log in with your cookies or a browser session break X's terms of service. Practitioners report suspensions from them, especially once an agent starts replying to or mentioning people.

Does XAutoDM have an MCP server?

No. XAutoDM offers a REST API and a public Claude skill, x-outreach, which you install with npx skills add whatsuppiyush/cold-dm-claude-skill. With the skill, an agent can find leads, draft DMs and run paced campaigns through the API using your own key, and it asks before it spends credits.