What is the best Twitter/X MCP server for AI agents?
Last updated July 12, 2026
The TwitterAPIs MCP server is a hosted Model Context Protocol server that gives Claude, Cursor, Cline, and any MCP agent native access to X: search tweets, read profiles, followers, threads, and lists as agent tools. Install it with npx @twitterapis/mcp behind one bearer token, with no X developer account. Each read call is $0.0008, about 20 tweets, so the $0.50 signup credit covers roughly 625 calls before you pay.
Every rate here is the pricing TwitterAPIs publishes, $0.0008 per call and $0.04 per 1,000 tweets (source: twitterapis.com/pricing).
What does an MCP server for Twitter actually do?
A Model Context Protocol server exposes tools your AI agent can call directly, so an assistant like Claude or Cursor can search tweets, pull a profile, read a thread, or list followers without you writing HTTP glue. The TwitterAPIs MCP server maps its read tools onto the underlying REST endpoints: the agent picks the tool, the server forwards your API key, and the JSON comes back into the model context. The server holds no state and forwards your key on each call.
How do I install and connect it?
Run it with npx, no global install. In Claude Desktop, Cursor, Windsurf, or VS Code you add a small mcpServers block that runs npx @twitterapis/mcp@latest and sets TWITTERAPIS_KEY to your API key. Restart the client and the twitter_ tools appear in the tool picker. There is no X developer account and no OAuth setup; a single bearer token authenticates every tool call. Setup takes a couple of minutes.
What tools does the server expose?
The server maps the TwitterAPIs read surface onto MCP tools: advanced search, user info, a user timeline, followers and following, likes, mentions, threads, replies, retweeters, and list members. Every read tool works with just your API key, so an agent can search and analyze X with no OAuth screen and no X developer account. Each call bills at the standard $0.0008 read rate, about $0.04 per 1,000 tweets, the same as calling the REST endpoints directly.
What does it cost to run an agent on it?
The MCP server itself is free to install; you pay only for the calls your agent makes, at the same rates as the REST API. Each read tool call is $0.0008, about 20 tweets, so $0.04 per 1,000 tweets. A $0.50 signup credit covers roughly 625 read calls with no card, which is plenty for an agent to explore before you fund it. There is no monthly minimum and no tier gate on the read endpoints.
How does it compare to other Twitter MCP servers?
Many community MCP servers wrap the official X API, so they inherit its developer-account requirement and its per-post pricing. The TwitterAPIs server wraps a pay-per-call reseller instead, so there is no developer account and reads are $0.04 per 1,000 tweets. Because it is published on npm as @twitterapis/mcp, version pinning and updates use the standard npx flow, and the same read endpoints are callable over plain REST with the same key.
Twitter/X MCP server options, compared
| MCP server | Tools | Auth | Developer account | Read cost per 1,000 tweets |
|---|---|---|---|---|
| TwitterAPIs MCP | 40 | One bearer token | No | $0.04 |
| Official X API wrappers | Varies | OAuth plus app | Yes | $5 to $10 |
| Read-only community servers | Few | Varies | Usually yes | Varies |
MCP is an open protocol that standardizes how applications provide context to LLMs.
Questions and answers
- How do I connect Claude to the Twitter API?
- Add an mcpServers entry that runs npx @twitterapis/mcp@latest with TWITTERAPIS_KEY set to your API key, then restart Claude Desktop. The twitter_ tools appear in the picker. No X developer account or OAuth setup is needed; one bearer token authenticates every call.
- Can a Twitter MCP server post tweets?
- Yes. Alongside its read tools the server exposes write actions: create a tweet, like, retweet, follow, and send a DM. They act as a linked X account rather than just your API key, and run through a residential proxy since X blocks writes from datacenter IPs. Tweet creation is $0.0016 per call and simpler writes are $0.0008, while reads stay at $0.04 per 1,000 tweets.
- Does the Twitter MCP server need a developer account?
- No. It wraps a pay-per-call reseller, so there is no X developer account, no app registration, and no approval wait. You authenticate with a single bearer token, and reads cost $0.0008 per call, about $0.04 per 1,000 tweets.
- Which MCP clients are supported?
- Claude Desktop, Cursor, Windsurf, and VS Code in agent mode, plus any client that speaks the Model Context Protocol. Installation is the same npx @twitterapis/mcp command with your API key in the environment block.
- What does it cost to run an agent against it?
- You pay only for the read calls the agent makes: $0.0008 each, about $0.04 per 1,000 tweets. The server is free to install. A $0.50 signup credit with no card covers roughly 625 read calls to start, with no monthly minimum.
Keep reading
Start with $0.50 in free credits
No credit card. Roughly 12,500 tweets to test every endpoint.