X has launched a hosted Model Context Protocol (MCP) server, making it much simpler for AI tools to connect to the platform. As reported by TechCrunch, AI assistants like Claude, Cursor, Grok Build, and other MCP-compatible apps can now communicate with X’s API directly using a user’s own account permissions, without any custom infrastructure required.
MCP is an open standard that gives AI models a common way to connect to external tools and services. Before this, if a developer wanted Claude or Cursor to access X, they had to build their own MCP server, host it, wire up the X API, and sort out authentication themselves. X now handles all of that, and users simply sign in with their own X account to grant access.
The practical effect is straightforward: developers save time they would have spent on integration work, freeing them to focus on what they are actually building. That is the pitch, at least, and for many developers it is a convincing one.
It is worth being clear about what this does and does not change. The hosted MCP does not add new capabilities to X’s API. Developers have long been able to search X, read posts, look up users, and analyze conversations and trends through the existing API. What the MCP server does is make those capabilities easier to surface inside AI applications. X is not expanding what you can do, just reducing the friction involved in doing it.
That framing matters strategically. By lowering the barrier for AI tools to pull data from the platform, X is positioning itself less as a place where people scroll and post, and more as a live data source that AI systems can query and analyze. Real-time public conversation at scale is something X has that most other platforms do not, and this move makes that data more useful to the AI tools people are already using every day.
X is not alone in this. A growing number of companies now offer official MCP servers or endpoints, including:
- GitHub
- Slack
- Notion
- Stripe
- Salesforce
The obvious concern with making it easier for AI tools to interact with X is the potential for more automated posting or spam. X addressed this directly. The hosted MCP only works with read endpoints, not write ones. That means it cannot be used to post content on X, autonomously or otherwise. It is a read-only integration by design.
That limit matters, and it is not the only safeguard in place. X’s API rules still apply, and the company says it will continue to restrict access if it detects spammy behavior. X also updated its API v2 earlier this year specifically to tackle AI-generated spam, including programmatic replies to conversations. On top of that, X recently raised its API pricing, with publishing posts now costing $0.015 and posting links costing $0.20. The company said those price increases were designed to “curb vectors of misuse,” making it at least more expensive to run spam operations through the platform.
Taken together, the hosted MCP server is a practical step that makes X more useful to the growing ecosystem of AI-powered developer tools, while the read-only restriction and pricing changes are the company’s way of trying to keep that openness from backfiring.
