Cloudflare's MCP servers just went stateless!

Hi, it's me! There's a small but important update in Cloudflare's Changelog, so let me walk you through it today!

Cloudflare Changelog developers.cloudflare.com

What was announced?

According to Cloudflare's Changelog, its product-specific MCP servers (for Agents, Workers, and more) now support the new MCP 2026-07-28 Specification! MCP is the protocol that lets AI agents talk to tools and services, and the spec itself just got updated, with Cloudflare following suit.

The story so far

Until now, when a client connected, it created an MCP protocol session tied to its own dedicated Durable Object. In other words, each connection meant a stateful object living somewhere, keeping track of that session.

What changes

With the new spec, every request now runs on a fresh, stateless server instead. There's no more MCP protocol session, and no more protocol-specific Durable Object needed!

The endpoints have been tidied up too:

• /mcp is now the standard endpoint for new connections
• The legacy /sse URLs keep working as aliases for the same Streamable HTTP handler
• That said, /sse no longer serves the deprecated HTTP+SSE transport
• Stateless requests from 2025-era Streamable HTTP clients are also accepted at /mcp

Most clients can reconnect without any configuration changes at all — pretty painless!

Dive Deep

One thing to watch out for: if a client is forcing the SSE transport, you'll need to switch it to Streamable HTTP or automatic transport detection. Other than that, your existing connection URLs (including /sse) should keep working as-is.

Wrap-up

• Cloudflare's MCP servers now support the MCP 2026-07-28 Specification
• Every request runs on a fresh, stateless server
• Use /mcp for new connections; existing /sse URLs still work as aliases
• Only clients forcing the SSE transport need a configuration change

If you're building agents or integrations on top of Cloudflare's MCP servers, now's a good time to double-check your connection settings!