X Launches Hosted MCP Server for Direct Connection to Claude, Cursor and Grok Build

X (formerly Twitter) launched a hosted MCP server — a Model Context Protocol server hosted on the platform's own infrastructure, which allows AI tools to connect directly to the X API using the access rights of the user's own account.

What the hosted MCP server can do

Multiple popular AI tools can connect to the server from the start, and the list is no longer limited to a single product.

• Supported tools at launch: Claude, Cursor, and Grok Build
• Connection works through access rights of the user's own X account
• Developers no longer need to write their own MCP server manually
• Previously, authorization for each AI tool had to be configured separately

The main practical effect is the elimination of all the preparatory integration work that developers used to do themselves: previously, to connect, for example, Claude to X data, you had to set up a server on your own that implemented the MCP protocol and separately solve the authorization issue. Now X provides a ready entry point, and the user simply grants access from their account.

Why the MCP protocol is needed

MCP, or Model Context Protocol, is an open standard that describes a single way to connect AI agents and tools like Claude or Cursor to external services and their data, instead of writing a separate integration for each specific AI tool. The launch of an official hosted server from X means the platform itself maintains and updates this entry point, removing from developers the task of maintaining their own infrastructure for the protocol.

In its announcement, X notes that with this move the company is joining other platforms that have already offered similar hosted MCP servers for their own APIs. This means that the practice of official hosting of MCP servers by API owners is gradually becoming the expected standard, not a rare exception.

For the end user, this looks like this: they grant access to their X account to an AI tool once, and then this tool can access their data on the platform directly — without intermediate services and without passing a password or token to third parties.

What this means

Hosting an MCP server directly from X is another step towards major internet platforms officially recognizing the MCP protocol as a standard for connecting AI agents to their APIs, lowering the barrier to entry for developers who want to build AI tools on top of X data.

For the AI agent ecosystem, this means that the list of services available to tools like Claude and Cursor without writing their own integration continues to grow, and the integration of AI agents with real user data becomes safer due to the use of built-in platform access rights rather than homemade workarounds.

Frequently asked questions

Which AI tools does the X MCP server support?

At launch, this is Claude, Cursor, and Grok Build — they can connect to the X API through the hosted MCP server without configuring their own integration.

Do developers need to write their own MCP server?

No — previously they had to do this themselves, now X provides a ready-made hosted server that takes care of both the protocol and authorization.

How does the MCP server get access to X user data?

Through the access rights of the user's own account — there is no need to configure separate custom authorization for each AI tool.