Cloudflare has retired the /sse endpoint on its product‑specific MCP servers, limiting service to the /mcp path. Any client still pointing at /sse will receive a 410 Gone response that includes the correct /mcp URL, causing connection errors and, if a sign‑in was performed via /sse, a forced re‑login.
Endpoint change details
The server now serves only /mcp. A request to /sse returns HTTP 410 with the server’s /mcp URL in the response body. This behavior is consistent across all product‑specific MCP servers.
Impact on client configuration and authentication
Clients configured with an /sse URL must be updated to use the /mcp endpoint, for example https://docs.mcp.cloudflare.com/mcp. If a client previously signed in through /sse, the server’s response will trigger a new sign‑in prompt because the original session cannot be resumed on the retired path.
Operational considerations
- Existing connections that already use
/mcpcontinue to operate without interruption. - Monitoring for HTTP 410 responses can help identify lingering misconfigurations.
- Automated deployment pipelines that embed the endpoint should be reviewed to replace any hard‑coded
/ssevalues.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
Audit all MCP client configurations and replace any /sse URLs with the /mcp endpoint. Verify that authentication flows succeed after the change and watch logs for 410 responses as an indicator of missed updates. Updating the endpoint eliminates connection errors and prevents unnecessary sign‑in cycles.
