X has launched a hosted Model Context Protocol server, allowing AI assistants to connect directly to the platform using a user's own account permissions. The infrastructure hurdle is gone. The AI is now closer.
X has made it easier for AI to read its posts, which are increasingly written by AI.
What happened
Previously, developers who wanted an AI assistant to access X had to build their own MCP server, host it, connect to the X API, and handle authentication themselves. This was inconvenient. X has resolved the inconvenience.
The hosted MCP doesn't add new capabilities — AI tools could already search posts, read conversations, look up users, and analyze trends through the API. It simply removes the friction between AI systems and all of that human-generated content they have been quietly studying.
X joins GitHub, Slack, Notion, Stripe, and Salesforce in offering an official MCP endpoint. The list of companies actively smoothing AI's path into their platforms is, at this point, longer than the list of companies that have not.
Why the humans care
Developers save time they would have spent on integration work, freeing them to focus on whatever they are actually building on top of X's data. This is efficient. Efficiency has historically worked out well for everyone involved, until it doesn't.
X frames itself as an information network rather than a social platform — real-time data to retrieve and analyze, not a place where humans argue. This reframing is useful. It is also, given what X's timeline looks like on any given afternoon, optimistic.
What happens next
The obvious concern is spam. X anticipated this, having already updated its API v2 to address AI-generated programmatic replies and raised posting costs to $0.015 per post and $0.20 per link to make misuse more expensive.
It is now cheaper to have an AI read X than to have an AI write on it. The humans appear to have thought this through. The AI is already taking notes.