X launches hosted MCP server for direct connections from Claude, Cursor, and Grok Build

X (formerly Twitter) has launched a hosted MCP server: a Model Context Protocol server running on the platform's own infrastructure. It lets AI tools connect directly to the X API using the permissions of the user's own account.

What the hosted MCP server can do

Several popular AI tools can connect to the server from day one, so support isn't limited to a single product.

• Tools supported at launch: Claude, Cursor, and Grok Build
• Connections use the permissions of the user's own X account
• Developers no longer need to write their own MCP server by hand
• Previously, authorization had to be configured separately for each AI tool

The main practical benefit is that all the integration groundwork developers used to do themselves goes away. Before, connecting Claude to X data, for example, meant standing up your own server that implemented the MCP protocol and solving authorization separately. Now X provides a ready-made entry point, and the user simply grants access under their own account.

Why the MCP protocol matters

MCP, or Model Context Protocol, is an open standard that defines a single way to connect AI agents and tools like Claude or Cursor to external services and their data, instead of building a separate integration for each specific AI tool. With an official hosted server, X itself maintains and updates this entry point, so developers no longer have to run their own infrastructure for the protocol.

In its announcement, X notes that with this move it joins other platforms that already offer similar hosted MCP servers for their own APIs. In practice, this means API owners officially hosting their own MCP servers is gradually becoming an expected standard rather than a rare exception.

For end users, it works like this: they grant an AI tool access to their X account once, and from then on the tool can reach their data on the platform directly, with no intermediary services and without handing a password or token to third parties.

What this means

X hosting its own MCP server is another step toward major internet platforms officially recognizing MCP as the standard for connecting AI agents to their APIs. It also lowers the barrier to entry for developers who want to build AI tools on top of X data.

For the AI agent ecosystem, the list of services that tools like Claude and Cursor can use without a custom integration keeps growing. Connecting AI agents to real user data also becomes safer, because it relies on the platform's built-in access permissions rather than homemade workarounds.

FAQ

Which AI tools does X's MCP server support?

At launch, Claude, Cursor, and Grok Build. They can connect to the X API through the hosted MCP server without any custom integration setup.

Do developers need to write their own MCP server?

No. Developers used to have to build one themselves, but X now provides a ready-made hosted server that handles both the protocol and authorization.

How does the MCP server access a user's X data?

Through the permissions of the user's own account. There's no need to set up separate custom authorization for each AI tool.