X launches hosted MCP server for AI tools

X has launched a hosted Model Context Protocol server that lets AI assistants connect to the platform using a user’s own account permissions, according to TechCrunch. The service is meant to remove the need for developers to build and run their own MCP server and to handle authentication plumbing just to let tools talk to the X API. X says the move is about making the platform easier for MCP-compatible apps—such as Claude, Cursor and Grok Build—to use.

The hosted server does not expand what the X API can do; it lowers the cost of exposing those existing capabilities to automated tools. Developers have long been able to search X, read posts, look up users and analyse conversations and trends via the API, and the MCP layer effectively standardises how an AI model calls those functions. In practice, that shifts X from being merely a place where humans post to a dataset that machines query and act on in real time.

That shift comes with an obvious second-order effect: if it becomes easier to wire AI agents into posting and replying, it also becomes easier to industrialise low-quality engagement. TechCrunch notes concerns that the hosted MCP server could increase automated posting or spam. X’s answer is that the MCP server still sits behind the platform’s API rules and enforcement, including restrictions when behaviour looks spammy.

But the platform has also been tightening the meter. TechCrunch reports that X recently increased API pricing, with publishing posts priced per post and posting links priced higher per link, and that the changes were intended to curb misuse vectors including spam. A hosted integration layer paired with higher marginal costs is a familiar pattern: make automation simpler, then charge for each automated action and reserve the right to cut off accounts that look abusive.

On Monday’s announcement, the new capability was not a novel feature so much as a new doorway. X is offering the handle, and it is charging for how often it gets turned.