Summary
On August 25, 2026, Cloudflare updated its MCP server portals to support the stateless MCP 2026-07-28 specification for both client and upstream server connections. The portal's /mcp endpoint automatically accepts stateless 2026-07-28 requests while staying compatible with earlier 2025 Streamable HTTP clients, and client-side and upstream protocol selection are independent so each can upgrade without portal reconfiguration (SSE connections keep the legacy protocol).
What changed
Cloudflare MCP server portals now speak the stateless MCP 2026-07-28 spec on both client and upstream connections; the /mcp endpoint auto-accepts stateless 2026-07-28 requests and still supports 2025 Streamable HTTP clients, with independent client/upstream protocol negotiation and legacy SSE unchanged.
Why it matters
Stateless MCP simplifies scaling and load-balancing of agent tool servers, and Cloudflare adopting it at the portal layer pushes the emerging standard toward production hardening. Combined with Workers SDK workflow controls, it strengthens Cloudflare's pitch as the runtime for agent tools and long-running workflows.
Evidence excerpt
MCP server portals support the stateless MCP 2026-07-28 specification for client and upstream server connections. The portal's /mcp endpoint automatically accepts stateless MCP 2026-07-28 requests and earlier 2025 Streamable HTTP clients ... client and upstream protocol selection are independent.