On June 30, 2026, X shipped something the ecosystem had been waiting for: X MCP — an official, hosted MCP server at api.x.com/mcp. Connect it to Claude and your AI assistant can search X in real time, pull trends, manage bookmarks, read timelines, and publish posts — through 200+ API endpoints, hosted by X itself, nothing to install on a server.
Most write-ups stop there, and that’s a problem — because the X MCP is genuinely different from the connectors we’ve covered so far. It’s not a one-click setup, and using it isn’t free. This guide covers what it actually is, the honest setup path, the pay-per-use math nobody puts up front, and who should (and shouldn’t) bother.
What Is X MCP?
MCP (Model Context Protocol) is the open standard that lets Claude connect to outside tools — our MCP Setup Guides directory covers every connector we’ve documented. X’s entry is a first-party, hosted MCP server: one endpoint that exposes the X API to any compatible AI client. There’s also a second server at docs.x.com/mcp that serves X’s developer documentation — useful if you build on the API, irrelevant for everyone else.
What makes it notable: X data is something a generic web search can’t replicate well. Real-time conversation search, trending topics by location, who’s driving a discussion — that’s proprietary signal, and this server is the sanctioned way for an AI agent to reach it.
Read This First: It’s Not a Two-Minute Setup
Unlike Shopify or Stripe, X is not in Claude’s connector directory — we checked the live directory before writing this. There’s no one-click Connect button. The official path requires:
- An X Developer account with an app created in the developer console (this is also where billing lives)
- Credentials and OAuth handled through a lightweight local bridge X provides (called
xurl) — it manages tokens for you, but you’re in terminal territory to set it up - A compatible client — Claude Desktop works, as do Cursor and VS Code. This is not the claude.ai web flow.
None of this is hard for a developer. For a creator who’s never opened a developer console, it’s a real step up from every other guide in our directory — and that’s before the pricing.
The Real Cost of X MCP (The Part Everyone Buries)
The MCP server itself is free. But every call it makes hits the X API, and since February 2026 the X API bills pay-per-use for new developers — the old free tier is gone, and the legacy $200/month Basic plan is closed to new signups. You load credits and pay per operation.
The rates that matter, as of the April 2026 update:
- Reading a post: $0.005 — and a search that returns 20 posts bills as 20 reads, not one call
- Reading your own data: $0.001 — your posts, followers, bookmarks are 5x cheaper
- Publishing a post: $0.015
- Publishing a post that contains a URL: $0.20 — yes, a link makes a post 13x more expensive
- Hard cap: 2 million reads/month — beyond that, the only option is an Enterprise contract in the tens of thousands per month
What this means in practice:
- Light personal use is genuinely cheap. Asking Claude to analyze your own recent posts and drafting a few tweets a week lands in single-digit dollars per month. No monthly floor, unlike the old $200 Basic.
- The URL trap is real. If your workflow is “share my new blog post with a link” — the most common creator automation there is — every one of those posts costs $0.20. Automate that across a month of daily posting and you’ve spent more than a scheduling tool costs.
- Research burns credits fast. “Analyze the last 1,000 posts about AI tools” = $5 in reads, every time you run it. Competitive monitoring at volume runs into hundreds per month.
How the Official Setup Works
If the math works for your use case, here’s the shape of the setup — we’re keeping this high-level because X’s own docs are the authoritative source and the flow updates frequently:
- Create an X Developer account at developer.x.com and set up an app inside a project. Add a payment method and load credits (pay-per-use requires a balance before any call works).
- Install X’s
xurlbridge and authenticate — it runs the OAuth flow and handles token refresh locally. - Add the server to your MCP client — in Claude Desktop, that means adding the hosted endpoint to your MCP configuration.
- Test with a cheap read: ask Claude to pull your own recent posts (owned reads are the $0.001 kind) before running anything search-heavy.
What It Unlocks When It’s Running
- “Search X for the last 24 hours of conversation about [topic], summarize the main takes, and list the accounts driving it” — the flagship use case, and something no generic web search does well
- “Pull trends for [location] and flag anything relevant to my niche”
- “Go through my bookmarks from this month and organize them by theme”
- “Draft a post about [X] and publish it” — works, just remember the $0.20 rule if it carries a link
Who It’s Actually For — and the Alternatives
Get it if: you’re comfortable with a developer console, your use case is read-light or centered on your own data, and you want first-party access to real-time X signal inside Claude.
Skip it if: you just want “Claude posts my content to X on a schedule.” The official server has no scheduling (the API doesn’t either), the URL pricing punishes exactly that workflow, and the setup friction buys you nothing. For that job, third-party managed layers (flat ~$10-15/month, no developer account) or a classic scheduler remain the pragmatic choice — we haven’t tested the managed MCP layers yet, so we’re not recommending a specific one, but the category exists and the pricing model fits creators better.
This is the same honest split we found with Instagram MCP: the official surface is built for one audience, and knowing which audience you are saves you money and an afternoon.
FAQ
Is X MCP free?
The server is free; the API calls it makes are not. X moved to pay-per-use pricing in February 2026 with no free tier for new developers — you pay per read and per post, from a credit balance.
Does it work with claude.ai in the browser?
It targets MCP clients like Claude Desktop, Cursor, and VS Code, with authentication handled through X’s local bridge. If you only use Claude in the browser, this connector isn’t built for your flow today.
Is there a monthly minimum?
No — that’s the upside of pay-per-use. Light usage costs single-digit dollars. The costs escalate with search volume and with posts that contain links.
You Might Also Like
More tested MCP guides from our directory:
Related Posts
