X Replaces Custom API Middleware With Native MCP Infrastructure

On June 30, 2026, X launched native Model Context Protocol (MCP) infrastructure, allowing AI tools to query real-time social data without custom middleware. By adopting the standard, X enables developers to connect agents directly to the platform’s API using existing account permissions. This removes the infrastructure tax previously required to build and maintain bridge servers for individual AI applications.

Dual-Server Architecture

The release splits functionality across two distinct hosted implementations to serve different developer workloads.

The Core API Server (api.x.com/mcp) exposes over 200 API endpoints. It handles read operations like searching posts within a seven-day window, fetching timelines, and retrieving conversations. Write capabilities include creating posts, replies, and quote tweets. The server also supports media uploads for standard image and video formats via the v2 upload API.

The Documentation Server (docs.x.com/mcp) provides programmatic access to the platform’s developer specifications. This allows coding agents to reference API schemas and integration guides in real time while writing implementation code.

Both servers use Streamable HTTP transport running protocol version 2025-06-18. Authentication is managed through OAuth 2.0 alongside a local bridge tool called xurl. This utility runs locally to handle token caching and automatic refreshes. Native compatibility is immediately available for Anthropic Claude, Cursor, Grok Build, and VS Code.

Bypassing Custom Middleware

If you build agents that interact with social data, native Model Context Protocol support changes your deployment footprint. Previously, connecting a model to X required building a custom API wrapper to handle authentication, rate limiting, and response formatting.

Architecture Phase	Integration Method	Authentication	Infrastructure Cost
Pre-MCP	Custom bridge server	Manual OAuth token management	High (Developer hosted)
Hosted MCP	Direct client connection	xurl automatic caching	Zero (Platform hosted)

This standardization solves the persistent integration bottleneck where models required custom code for every distinct tool they needed to use. Developers can now utilize zero-configuration access.

Rate Limits and Constraints

While the transport layer has changed, the underlying business logic remains untouched. Developers must register an application through the developer portal to obtain credentials. All rate limits and data access restrictions are strictly bound to your existing API tier. If you operate on the Free or Basic tier, the MCP endpoints will enforce the same monthly post caps and search constraints as the standard REST API.

X maintains its existing anti-abuse systems across the new infrastructure. Automated spam filters and account restrictions apply equally to agent-generated content.

When migrating existing workflows to the hosted server, replace your custom bridge deployment with the xurl utility and update your agent configurations to point directly to the new endpoints. Ensure your API tier provides sufficient capacity for the automated request volume your agent will generate.