Overview
On July 28, 2026, the Model Context Protocol (MCP) working group published the 2026-07-28 specification — <cite index="3-2">the largest revision of the protocol since its launch.</cite> MCP is an open standard, <cite index="3-6,3-7">that enables Artificial Intelligence (AI) models to connect to external data sources and tools securely, introduced by Anthropic to standardize the integration between AI applications and local or remote systems.</cite> The new specification was authored by lead maintainers David Soria Parra and Den Delimarsky and is governed under the Agentic AI Foundation (AAIF), <cite index="16-1">a directed fund under the Linux Foundation.</cite>
Stateless Core
<cite index="10-7,10-8">The highlight of the release is a stateless protocol core — MCP is transforming from a bidirectional stateful protocol into a request/response stateless protocol. It was one of the most highly-requested features from developers who were eager to get better reliability and scalability for their MCP servers.</cite>
<cite index="3-10,3-11,3-12">The 2026-07-28 revision removes both the initialize handshake and the protocol-level session. Every request is now self-contained. The protocol version, client information, and capabilities are included in each request rather than exchanged once at connection time.</cite> <cite index="3-14,3-15">Because there is no session identifier, any request can be routed to any server instance. Operators can place an MCP server behind a simple round-robin load balancer without sticky sessions or a shared session store.</cite>
<cite index="11-2,11-3">MCP moves from a bidirectional stateful protocol to a request/response model, and servers can now deploy on serverless and edge infrastructure.</cite> Previously, <cite index="13-10,13-11">horizontal deployments were forced to use sticky sessions or a shared session store like Redis, and serverless and edge deployments were essentially off the table.</cite>
New Capabilities
<cite index="2-1">The 2026-07-28 specification brings a stateless protocol core, Multi Round-Trip Requests (MRTR), header-based routing, cacheable list results, authorization hardening, a formal extensions framework, and updated Tier 1 Software Development Kits (SDKs).</cite>
<cite index="13-6">Three official extensions ship with the release: MCP Apps (server-rendered User Interface), Tasks (asynchronous and long-running operations), and Enterprise Managed Auth (Identity Provider-based organization-wide provisioning).</cite> <cite index="11-12">Authorization now aligns with production OAuth 2.0 and OpenID Connect (OIDC) deployments, so MCP servers can connect to enterprise identity systems without workarounds.</cite>
<cite index="13-7">Breaking changes include deprecation of Roots, Sampling, Logging, HTTP+Server-Sent Events (SSE) transport, and Dynamic Client Registration, with a 12-month removal window.</cite>
Ecosystem Adoption
<cite index="11-4">MCP recently surpassed 400 million monthly SDK downloads, a 4x increase in 2026, and has become the industry standard for connecting AI agents to applications.</cite> <cite index="13-8">All four Tier 1 SDKs — TypeScript, Python, Go, and C# — are updated as of the release date.</cite>
Ecosystem adoption was broad at launch. <cite index="19-3,19-4">Cloudflare's Agents SDK supports the specification from day zero, so developers can run MCP servers directly in Workers without transport-session overhead; Cloudflare customers including Sentry and Linear can adopt it immediately.</cite> <cite index="9-1,9-2">The GitHub MCP Server also shipped support for the new stateless specification ahead of the official release date.</cite> Figma, Zoom, Intuit, and Netlify are among partners quoted in the official Anthropic announcement as supporting the updated specification at launch.
<cite index="11-18">Claude now lists over 950 MCP servers in its connectors directory, used by millions of people every day,</cite> and <cite index="4-2">support for the new specification is rolling out across Claude products.</cite>
Migration and Compatibility
<cite index="24-7">A remote MCP server that previously needed sticky sessions, a shared session store, and deep packet inspection at the gateway can now run behind a plain round-robin load balancer, route traffic on an Mcp-Method header, and let clients cache tools/list responses for as long as the server's ttlMs permits.</cite> <cite index="1-12,1-13">The stateless rework is a foundational change that required a clean break; with it in place, and with deprecation windows and extensions as the standard tools going forward, implementers targeting 2026-07-28 should be able to adopt future revisions without rewriting their transport or lifecycle code.</cite>