Cloudflare MCP server portals now bridge 2026-07-28 clients and legacy upstreams independently

Cloudflare's MCP server portals, the Cloudflare One feature that fronts multiple MCP servers behind a single governed endpoint, now speak the 2026-07-28 revision. The change went out in a developers changelog entry dated 2026-08-25.

The design is a bridge rather than a cutover. A portal's /mcp endpoint accepts stateless 2026-07-28 requests and earlier 2025 Streamable HTTP clients at the same time, and on the other side it checks each upstream server for 2026-07-28 support, falling back to the 2025 handshake where the upstream has not moved. The entry makes the operational consequence explicit: client and upstream protocol selection are independent, so clients and servers can upgrade separately without portal configuration changes. One boundary is stated: SSE connections continue to use the legacy protocol.

A portal sits in front of fleets of servers, so an intermediary that negotiates each side separately addresses the coordination problem of a stateless-core migration: an organization's clients and servers rarely upgrade on the same schedule. Cloudflare's own MCP servers adopted 2026-07-28 in July; the portals feature previously appeared in our coverage when it gained static OAuth client credentials for upstreams without dynamic client registration.