X launches official hosted MCP server
X's new hosted MCP server lets Claude, Cursor, and Grok Build connect to the X API using a user's own account. No custom server to build or host.
X announced a hosted Model Context Protocol server on June 30, giving AI assistants (Claude, Cursor, and Grok Build) official access to the X API through a user’s own account permissions.
The server exposes existing X API functionality: searching posts, reading content, looking up users, and analyzing conversations and trends. X handles the infrastructure; developers do not need to build, host, or authenticate their own MCP server.
Writing via the API still costs money. Publishing a post costs $0.015; posts with links cost $0.20. X says the pricing is designed to curb spam, and the hosted MCP still enforces existing API restrictions on spammy behavior. The server does not add new X API capabilities; it surfaces the existing ones with an MCP interface.
Why this matters
Until now, using X data in AI workflows meant building your own server, scraping (high ToS risk), or paying for a costly Enterprise API tier. The hosted MCP removes the infrastructure burden and gives developers a clear, permitted path to pulling real-time X data into an agent workflow.
Practical uses: competitive monitoring (watch mentions of a product or competitor), trend detection before publishing, audience research, and testing whether a draft resonates with current X conversations. The per-post cost makes write operations expensive for bulk use but is low enough for targeted agent actions.
The X MCP follows a growing wave of official MCP integrations from major platforms. Earlier this month, Mistral opened its connectors to API use, and Runlayer raised $30 million specifically to add security and governance around MCP deployments, a signal that operators are building production pipelines here, not just experiments.