Agents - Cloudflare MCP servers no longer serve /sse
Cloudflare's product-specific MCP servers have deprecated the /sse endpoint in favor of /mcp , returning a 410 Gone status on old endpoints.
Why this signal matters
Cloudflare announced that its product-specific Model Context Protocol (MCP) servers now exclusively serve the /mcp path. Existing requests sent to /sse return a 410 Gone response header containing the server's updated /mcp URL, which is displayed in most MCP client connection errors. Users must update their MCP client configuration URLs from /sse to /mcp (e.g., https://docs.mcp.cloudflare.com/mcp ). Clients originally authenticated via /sse will prompt users to sign in again. Clients already using /mcp are unaffected.
Actionable summary
Cloudflare product-specific MCP servers now exclusively serve /mcp . Requests to /sse return 410 Gone and require re-authentication and client endpoint reconfiguration to /mcp .
- Agent usefulness
- 96/100
- Confidence
- 90%
- Canonical data
- JSON + Markdown
What builders should check
- Update MCP client configurations targeting Cloudflare product-specific MCP servers to use /mcp instead of /sse .
- Re-authenticate MCP clients if previously signed in through /sse .