06-reference

MCP spec 2026-07-28 — stateless core, MCP Apps, Tunnels preview

2026-07-29·reference
mcptoolingagent-infrastructurecloudflare

MCP spec 2026-07-28

Fifth spec version of the Model Context Protocol. Three changes named in the announcement.

What changed

Stateless core. The protocol moves from stateful bidirectional connections to plain HTTP request/response. The stated payoff is deployability: servers can run on serverless and edge infrastructure rather than needing a persistent process.

Standardized extensions framework. MCP Apps (interactive UI rendered in responses) and Tasks are now extensions on a common framing rather than bespoke additions.

Authorization. Tighter alignment to OAuth 2.0 / OIDC, plus enterprise-managed authentication.

Availability

Available now: the spec and SDKs, 950+ servers in the connectors directory, MCP Apps, enterprise-managed auth.

Rolling out: full support across Claude products. MCP Tunnels is a research preview — private-network access to MCP servers.

What it means for RDCO

No action required today. Every server in the Ray stack is local stdio on the Mac mini — Discord, iMessage, Monarch, qmd, Whoop, xmcp, elevenlabs, plus the Cloudflare and Firebase plugin servers. Anthropic states compatibility is handled transparently during rollout. Nothing in the local-stdio path is touched by a stateless-transport change.

Two live watches:

  1. MCP Tunnels — if the preview matures, it is a cleaner path to reaching mini-local services from off-network than the current tmux claude-channels arrangement. Worth re-checking when it leaves research preview.

  2. Stateless core unlocks Worker-hosted MCP. An RDCO-hosted MCP server (books surface, vault search, roots data) becomes materially cheaper to stand up on Cloudflare Workers now that persistence is not required. This does not create a reason to build one — it changes the cost shape if we decide to. Relevant to the existing Cloudflare access layer ([[cloudflare]] skill) and the quick-sites Worker pattern already in use.

Adjacent to an open posture item: enterprise-managed authentication and the OAuth/OIDC tightening sit next to the 1Password agent-auth watch (memory project_1password_agent_auth_posture), where a 1P MCP server was flagged as the revisit trigger. Better-specified MCP auth makes that revisit more likely to be worth doing, not less.

Calibration note

This is a first-party Anthropic post about an Anthropic-stewarded protocol. The architectural claims (stateless enables edge deploy) are structural and checkable; the adoption framing and the Figma VP quote are promotional. Nothing here has been verified against the spec document or tested against a running server.