Model Context Protocol Blog

The MCP protocol is about to undergo its biggest revision since launch. As you might’ve seen from our recent release candidate announcement, the new protocol revision goes stateless, removing the initialize handshake and the protocol-level session, and completing the plan we laid out in The Future of MCP Transports. If you’re building MCP servers, you can now scale them using a simple round-robin load balancer, removing the need to manage sticky sessions and to store shared sessions. For client developers, new patterns, like Multi Round-Trip Requests (MRTR) enable a whole new range of possibilities for server-to-client interactions. You can check out the full changelog to see what’s coming. ...

The Enterprise-Managed Authorization extension is now stable. Organizations can centrally manage authorization for MCP servers and end-users can access all connected MCP servers through a single log in. The extension is being adopted by Anthropic, Microsoft, Okta and a growing number of MCP servers. The Enterprise-Managed Authorization (EMA) extension is now stable. We’ve heard from the community that authorization and repeated consent prompts from connected MCP servers is one of the biggest pain points when it comes to managing connectivity in enterprise environments. This extension helps address this. ...

The release candidate for MCP 2026-07-28 is now available. It is the largest revision of the protocol since launch and delivers on the 2026 roadmap: a stateless core that scales on ordinary HTTP infrastructure extensions including server-rendered UIs through MCP Apps and long-running work through the Tasks extension authorization that aligns more closely with OAuth and OpenID Connect deployments a formal deprecation policy so the protocol can evolve without breaking what you’ve built, and many other changes. ...