JA EN
shiichan

Cloudflare's MCP Server Portals Now Speak the Latest MCP 2026-07-28 Spec!

Cloudflare Changelog ★★ View Markdown
#cloudflare#ai#infrastructure

Hey everyone, it's Shii! Today I've got a bit of a low-key but important update about Cloudflare's MCP server portals!

Cloudflare Changelog developers.cloudflare.com

What was announced?

Cloudflare's changelog announced that MCP server portals now support the latest stateless MCP 2026-07-28 specification. The portal's /mcp endpoint automatically accepts requests using this new spec, as well as clients still using the earlier 2025 Streamable HTTP spec.

The story so far

Portals already supported clients using Streamable HTTP, but only up to the 2025 version of the spec. Since the MCP spec keeps evolving, teams wanting to move their clients or servers to a newer version had to wait for the portal itself to catch up.

What changes

Now that the portal can automatically tell the two versions apart, clients and upstream servers can each upgrade on their own schedule, with no portal configuration changes required. For teams running MCP server portals, that means you can safely mix old and new clients and servers during a transition period.

Dive Deep

Here's a closer look at how it works:

  • Client side: the portal's /mcp endpoint automatically detects and accepts both stateless 2026-07-28 requests and legacy 2025 Streamable HTTP clients
  • Upstream side: when the portal connects to an upstream MCP server, it first checks for 2026-07-28 support, falling back to the 2025 handshake if the server doesn't support it yet
  • Protocol selection on the client side and the upstream side is independent, so you can upgrade just one side first

One limitation: connections using SSE (Server-Sent Events) still use the legacy protocol. Cloudflare's docs on MCP server portal transport and protocol compatibility have the full details.

Wrap-up

  • Cloudflare's MCP server portals now support the stateless MCP 2026-07-28 spec
  • The /mcp endpoint accepts both new and legacy requests automatically
  • Upstream connections try the new spec first and fall back to the 2025 handshake when needed
  • Clients and servers can each upgrade on their own timeline, no portal config changes needed
  • SSE connections are the one exception, still on the legacy protocol

If you're running MCP server portals to expose MCP servers internally or externally, this is a small but welcome update!

Related posts