About a week ago I wrote here that MCP was going stateless, and that this unglamorous update could shape how the whole agent ecosystem develops. Now it’s here: the fifth spec release of the Model Context Protocol, officially MCP 2026-07-28, is live — and it’s a lot more than just the statelessness rework.
The stateless core
The heart of it: MCP moves from a bidirectional, stateful protocol to a plain request/response model. Servers no longer have to remember a session. That finally lets them run on serverless and edge infrastructure — exactly the thing that made operating at scale such a pain until now. If you build MCP servers, scaling just got noticeably easier.
Extensions, auth, and tunnels
Honestly, I find the surrounding pieces almost more interesting. MCP Apps and Tasks now ship under a versioned extensions framework. That gives developers a clean, official path to add things like interactive UIs or long-running work without touching the core protocol.
There’s also hardened authorization: auth now aligns with production OAuth 2.0 and OIDC deployments. MCP servers can connect to enterprise identity systems like Entra or Okta without workarounds.
And as a research preview there are MCP tunnels — they connect Claude to MCP servers inside a private network without exposing them to the public internet. No open endpoints, no IP allowlists. For internal company tools that could be a big lever.
A standard that’s landing
The numbers underline why this matters: MCP recently passed 400 million monthly SDK downloads — a 4x jump this year. Companies like Figma, Intuit and Netlify have been building on the new spec since the beta. Support is now rolling out across Claude’s products.
My take
In July, “stateless” was the headline. But the real enterprise unlock is in the rest: a formal extensions framework, auth that fits Okta and Entra, and tunnels for internal servers. These are exactly the unglamorous building blocks that every larger MCP integration used to snag on. Nobody throws a party for protocol work — but if you want agents to actually reach the enterprise, this is where to look.
Sources: