signal insight

Cloudflare adopts the MCP 2026-07-28 spec across its hosted MCP servers and Agent…

In late July 2026, Cloudflare shipped support for the newly finalized Model Context Protocol 2026-07-28 specification across both its hosted MCP servers and Agents SDK v0.20.0. The update brings stateless MCP requests that work without protocol sessions, client- and server-side support for tools, prompts, resources, and elicitation, OAuth callback validation, and legacy compatibility — historical SSE URLs keep working as aliases, and there is a documented migration path from McpAgent and SDK v1.

Published Jul 27, 2026 Updated Jul 29, 2026 2 sources

CloudflareCloudflare Agents SDKagentsfeature launchmedium impact

agentsai-coding-toolsenterprise-controlsfeature launch

Impact: medium
Confidence: 85%
Change type: feature launch
First seen: Jul 27, 2026
Last updated: Jul 29, 2026
Audience: platform-engineersagent-developersai-infrastructure-leaders
Status: Ready

Summary

What changed

Cloudflare's hosted MCP servers (changelog dated 2026-07-28) and Agents SDK v0.20.0 (dated 2026-07-27) added client and server support for the MCP 2026-07-28 spec, including stateless Workers-native tools/prompts/resources/elicitation and backward-compatible SSE aliasing.

Why it matters

Cloudflare is one of the first major platforms to implement the finalized MCP 2026-07-28 spec in production, and doing it statelessly fits the Workers execution model where per-session servers are awkward. It lets developers build MCP servers and agents on Cloudflare that are immediately compatible with the new spec while keeping older SSE clients working, lowering the migration cost of the standard's stateless rewrite.

Evidence excerpt

Cloudflare MCP servers now support the new MCP 2026-07-28 specification; stateless requests work without protocol sessions and historical SSE URLs continue functioning as aliases. Agents SDK v0.20.0 adds client and server support for the MCP 2026-07-28 release candidate.