MCP 2026-07-28 Spec Locks: Stateless Revolution Reshapes OpenClaw Infrastructure

The Model Context Protocol specification for the 2026-07-28 release candidate was locked on May 21, 2026 — and for anyone running OpenClaw with MCP server infrastructure, this is the most consequential spec revision since MCP launched. The final spec ships July 28, giving infrastructure teams roughly 10 weeks to migrate.

What’s Changing

The headline change is a full stateless overhaul:

  • No more initialize handshake — metadata travels in _meta on every request
  • Session IDs are removed — servers can sit behind plain round-robin load balancers
  • New required headers (Streamable HTTP): Mcp-Method and Mcp-Name let API gateways route and rate-limit without inspecting the body
  • Servers must now reject requests where headers disagree with the body

The extension framework has also been structurally improved. Extensions now carry reverse-DNS identifiers, their own ext-* repositories, and independent versioning. Two official extensions ship at launch: MCP Apps (server-rendered HTML in sandboxed iframes) and Tasks (long-running work via tasks/get, tasks/update, tasks/cancel).

Other notable changes: full JSON Schema 2020-12 support, client-side caching with ttlMs/cacheScope on tools/list, and OAuth hardening requiring iss validation per RFC 9207.

What Gets Deprecated (Eventually)

Three features are annotation-only deprecated with a 12+ month window:

  • Roots → tool parameters
  • Sampling → direct LLM integration
  • Logging → OpenTelemetry

No immediate action is required, but new MCP projects should design around the future direction.

Enterprise Adoption Continues Accelerating

Despite — or because of — the protocol shakeup, enterprise MCP adoption is growing:

  • ServiceNow Action Fabric MCP Server reached GA
  • Microsoft Copilot Studio launched remote MCP servers with Entra ID
  • Anthropic released self-hosted sandboxes for Claude inside customer-controlled environments

What OpenClaw Users Need to Do

For OpenClaw deployments running session-based MCP servers: the window between now and July 28 is the migration period. Start refactoring session-state logic now. The full spec is on modelcontextprotocol.io.

OpenClaw’s June release train (2026.6.x) already ships with the architectural foundations needed to support the new spec — but MCP server operators need to update their server implementations independently.

← Back to News