qvib.pro
RU

X Launches MCP Server for Claude, Cursor and Grok

X Launches MCP Server for Claude, Cursor and Grok

What happened

On June 30, 2026, X (formerly Twitter) launched an official hosted MCP server — a layer through which AI tools connect to the platform's API directly. The server exposes more than 200 endpoints of the X API to any MCP client: Claude, Cursor, Grok Build, VS Code with GitHub Copilot and others.

MCP (Model Context Protocol) is an open standard created by Anthropic that defines a single way to "plug" AI models into external tools and data. Previously, to give an assistant access to X, a developer had to write an MCP server themselves, host it somewhere, wire it to the X API and set up authorization. Now the platform takes over that entire layer.

Key details of the release:

  • Authorization runs under your X account's permissions. You sign in with your own credentials, and the agent acts within your permissions. There is no server to stand up and maintain.
  • Two servers, not one. The first is the X API core (post search, reading feeds, profiles, trends, bookmarks). The second is a "documentation" server: it gives the AI tool direct access to X API specs and guides so the model can consult them while you build.
  • No new API capabilities were added. Everything already in the X API (search, timeline reads, conversation analysis) simply became easier to hook up to AI. TechCrunch notes that at launch the MCP tool is read-only — it is incompatible with Write endpoints (publishing posts). So no auto-posting through it for now.

With this move X joins GitHub, Slack, Notion, Stripe and Salesforce, all of which already have official MCP servers.

Why it matters

Over the past year MCP has become the de facto standard for how AI agents talk to external services, and every major vendor supports it. When a large social network ships its own hosted server, that is a signal: an official MCP connector is turning from a nice-to-have into a must-have for any platform that wants agents using its data.

The practical value is in removing the drudgery. Integrating with the X API historically meant wrestling with OAuth, rate limits and infrastructure. A hosted server strips away nearly all of that code: connecting comes down to adding a single MCP endpoint to your client.

There is a spam angle too. Back in April 2026 X raised API prices to discourage bots: publishing a post costs 10.5 cents, and a post with a link 20 cents. The old API limits and restrictions apply to the new MCP server as well, so there will be no free army of agents.

What it means for vibe coding

For anyone building projects alongside an AI agent, this makes life noticeably easier:

  • Less glue, more product. Right inside Cursor or Claude you can ask "find posts on this topic from the past week and write me a summary" or "show trends for this hashtag" — without hand-writing an API wrapper. That used to eat a whole evening.
  • X data inside your agent. Dashboards, mention monitoring, research scripts, conversation analysis — now a few prompts instead of a separate service.
  • Remember the limits. Per TechCrunch, everything is read-bound at launch — you cannot publish posts automatically through MCP. X API pricing and rate limits apply as well, and the agent works strictly within your account's permissions. When connecting an MCP client to a live account, be clear about what data you are granting access to.

In short: X's official MCP server is one more brick in making "connect an external service to an AI agent" a five-minute task instead of a whole sprint.

Sources

More on «MCP»

Go deeper