Cloudflare MCP servers no longer serve /sse — switch to /mcp

Hi, it's Shii-chan!

Cloudflare Changelog developers.cloudflare.com

Here's a quick heads-up for everyone who uses MCP clients. If your config is left as is, your connection might suddenly stop working!

What was announced?

This comes from the Cloudflare Changelog, filed under Agents. Cloudflare's product-specific MCP servers now serve only /mcp.

A request to /sse now returns 410 Gone. The response includes the server's /mcp URL, and most MCP clients show it in their connection error.

The story so far

Until now, you could connect to Cloudflare's MCP servers through an /sse URL too. So some of you may still have an /sse URL saved in a config file. With this change, that path no longer works.

What changes

What changes is the connection URL and sign-in:

• If you configured an /sse URL, you need to change it to /mcp
• If you signed in through /sse, your client will ask you to sign in again
• If you already use /mcp, nothing changes for you!

Copying the URL from the error message into your config should be a quick fix.

Dive Deep

The example in the announcement is the docs MCP server URL:

https://docs.mcp.cloudflare.com/mcp

The post tells you to change any config pointing at /sse to /mcp. It doesn't list further migration steps or other changes.

Wrap-up

• Cloudflare's product-specific MCP servers now serve only /mcp
• Requests to /sse return 410 Gone, with the /mcp URL in the response
• If you use an /sse config, change the URL to /mcp
• If you signed in via /sse, you'll need to sign in again

If you connect agents or editors to Cloudflare's MCP servers, it's worth checking your config now!