MCP 2026-07-28 Moves to a Stateless Core as Claude Rolls Out Support

Anthropic says the MCP 2026-07-28 specification is live, moving the Model Context Protocol from a bidirectional stateful protocol to a request/response model with a stateless core. The Claude developer account says the change makes remote MCP servers easier to deploy and scale. (ClaudeDevs on X)

The announcement is the fifth MCP specification release. Anthropic says support is being rolled out across Claude products, so the protocol update is both an infrastructure change for MCP developers and a forthcoming product-surface change for Claude users. (Anthropic's MCP announcement)

What changed in the protocol

The headline change is the shift away from a bidirectional stateful design. Anthropic says the new request/response model introduces a stateless core, allowing servers to deploy on serverless and edge infrastructure without carrying the same stateful assumptions into every connection. (Anthropic's MCP announcement)

The release also puts MCP Apps and Tasks under a versioned extensions framework. Anthropic describes that framework as a formal path for adding capabilities such as interactive interfaces and long-running work without changing the core protocol. (Anthropic's MCP announcement)

For users, MCP Apps can render interactive UI directly inside a conversation. Anthropic says users can see what a connector is doing and work with it inline instead of switching tabs. (Anthropic's MCP announcement)

Authentication is aimed at production deployments

MCP authorization now aligns with production OAuth 2.0 and OIDC deployments. Anthropic says MCP servers can connect to enterprise identity systems such as Entra and Okta without the workarounds that were previously needed. (Anthropic's MCP announcement)

Anthropic also describes enterprise-managed auth for MCP connectors. An administrator can authorize a connector once, users can inherit access through existing identity-provider groups, and the connector can be connected on first login. The page presents this as zero-touch setup for the end user. (Anthropic's MCP announcement)

What it means for Claude builders

If you maintain an MCP server, the stateless core is the architectural change to investigate first. Serverless and edge deployment can simplify operations, but the right migration plan depends on how your server currently handles sessions, request state, retries, and authorization.

If your integration needs a UI or work that continues beyond one request, MCP Apps and Tasks provide a versioned extension path rather than requiring a change to the core protocol. The practical question is whether your client surface and deployment target support the extension you want to use.

Anthropic also lists MCP tunnels as a research preview. The tunnels connect Claude to MCP servers inside a private network without exposing those servers to the public internet, inbound firewall rules, public endpoints, or IP allowlisting on the origin. (Anthropic's MCP announcement)

Rollout status and ecosystem scale

Anthropic says support for MCP 2026-07-28 is rolling out across Claude products rather than claiming that every surface has switched over. Its announcement says Claude's connectors directory lists more than 950 MCP servers, used by millions of people every day. (Anthropic's MCP announcement)

For teams, the near-term action is to read the 2026-07-28 specification, review the state and auth assumptions in existing servers, and watch the Claude product surfaces where you need MCP Apps, Tasks, or enterprise-managed connectors. The protocol is live, but product support is still in rollout.

Sources

• ClaudeDevs announcement: https://x.com/ClaudeDevs/status/2082164248697069935
• Anthropic MCP 2026-07-28 announcement: https://claude.com/blog/bringing-mcp-2026-07-28-to-claude