
/sse Returns 410 Gone on Cloudflare's Per-Product MCP Servers: Verifying the Switch to /mcp and How It Appears in Claude Code
This page has been translated by machine translation. View original
Hello! I'm Yuji Nishimura from the Operations Department!
On October 22, 2026, Cloudflare's product-specific MCP servers stopped serving /sse and now offer only /mcp (Cloudflare Changelog). MCP clients that still have a /sse URL configured, such as https://docs.mcp.cloudflare.com/sse, can no longer connect.
In this article, I use curl to check what /sse and /mcp actually return, and also look at how this appears in Claude Code. Then I walk through the steps for switching your configuration to /mcp.
Product-specific MCP servers dropped /sse and now offer only /mcp
- Date: October 22, 2026
- Scope: the product-specific MCP servers under
*.mcp.cloudflare.com, such asdocs.mcp.cloudflare.comandbindings.mcp.cloudflare.com - Change:
/ssereturns410 Gone, and the response includes the destination/mcpURL - Required action: change the URL in your client configuration from
/sseto/mcp. According to the Changelog, if you had signed in via/sse, you will be asked to sign in again - Not affected: the Changelog states that configurations already connecting via
/mcpare not affected
Cloudflare's documentation directs you to connect to each server through the Streamable HTTP endpoint /mcp. The Cloudflare API MCP server (https://mcp.cloudflare.com/mcp), which covers the entire API, is not affected by this change.
According to cloudflare/mcp-server-cloudflare#505, which introduced the change, the reason is that the OAuth library (@cloudflare/workers-oauth-provider) was upgraded to the 1.x series. In 1.x, a token can be bound to only one resource. Making the resource the entire origin would protect both /mcp and /sse, but it would invalidate all existing authorizations for /mcp. The PR therefore explains that the resource was set to <origin>/mcp and /sse was retired. The reason it returns 410 instead of redirecting is that a redirect would only help API token users, and OAuth users would not learn that they need to migrate to /mcp.
Trying it out
Environment
- macOS 26.6.1 (arm64)
- curl (bundled with macOS)
- Claude Code 2.1.300
- Verification date: October 25, 2026 (JST)
No credentials were used. I did not log in to a Cloudflare account or go through the OAuth authorization flow.
1. /sse returns 410 Gone and the destination URL
I sent a request to /sse on the documentation search server.
curl -s -i https://docs.mcp.cloudflare.com/sse
HTTP/2 410
content-type: application/problem+json
link: <https://docs.mcp.cloudflare.com/mcp>; rel="alternate"
{"type":"https://developers.cloudflare.com/agents/model-context-protocol/cloudflare/servers-for-cloudflare/","title":"This MCP URL has moved to /mcp","status":410,"detail":"The /sse URL is no longer served. Update your MCP client configuration to https://docs.mcp.cloudflare.com/mcp.","url":"https://docs.mcp.cloudflare.com/mcp"}
(Some headers are omitted.)
The status is 410, and the body is in the problem+json format (RFC 9457), which returns error details as JSON. The destination /mcp URL is included in detail and url, and the same URL is also attached to the link header with rel="alternate". Opening it in a browser shows the same JSON.

2. /sse returns 410 on all 17 servers
For the 17 servers listed in the README of cloudflare/mcp-server-cloudflare, I compared the status of a GET to /sse with the status of a request to /mcp. To /mcp, I sent the initialize request that MCP sends at the start of a connection, without authentication.
curl -s -o /dev/null -w '%{http_code}\n' -X POST \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl-check","version":"0.0.1"}}}' \
https://docs.mcp.cloudflare.com/mcp
| Server | /sse |
/mcp (no authentication) |
|---|---|---|
| docs, blog, demo-day | 410 | 200 |
| ai-gateway, auditlogs, autorag, bindings, browser, builds, casb, containers, dex, dns-analytics, graphql, logs, observability, radar | 410 | 401 |
/sse returned 410 for every server. The servers where /mcp returned 401 are the ones that require OAuth, and for all 14 of them the www-authenticate header in the response contained resource_metadata="https://<host>/.well-known/oauth-protected-resource/mcp".
Note that 10 of the 17 servers, including bindings, builds, observability, and radar, are marked as deprecated (Deprecated servers) in the README, and migration to the Cloudflare API MCP server is recommended. If you were using a deprecated server via /sse, you will need to choose between switching to /mcp and moving to the API MCP server.
The documentation's product-specific list also includes a server for the Agents SDK documentation (agents.cloudflare.com/mcp), but that one and the API MCP server's /sse returned 404, not 410, at the time I tried. The servers that return 410 are the product-specific servers under *.mcp.cloudflare.com.
3. In Claude Code, a /sse configuration shows "Failed to connect"
I checked how this looks on the MCP client side using Claude Code's claude mcp list. In a test directory, I added servers for /sse and /mcp and displayed their connection status.
claude mcp add --scope local --transport sse cf-bindings-sse https://bindings.mcp.cloudflare.com/sse
claude mcp add --scope local --transport http cf-bindings-http https://bindings.mcp.cloudflare.com/mcp
claude mcp add --scope local --transport sse cf-docs-sse https://docs.mcp.cloudflare.com/sse
claude mcp add --scope local --transport http cf-docs-http https://docs.mcp.cloudflare.com/mcp
claude mcp list
cf-bindings-sse: https://bindings.mcp.cloudflare.com/sse (SSE) - ✘ Failed to connect — HTTP 410: SSE error: Non-200 status code (410)
cf-bindings-http: https://bindings.mcp.cloudflare.com/mcp (HTTP) - ! Needs authentication
cf-docs-sse: https://docs.mcp.cloudflare.com/sse (SSE) - ✘ Failed to connect — HTTP 410: SSE error: Non-200 status code (410)
cf-docs-http: https://docs.mcp.cloudflare.com/mcp (HTTP) - ✔ Connected
The two /sse entries show Failed to connect, and what is displayed goes only as far as Non-200 status code (410). When the transport is sse, the destination URL in the response body did not appear in this list. The verification table in PR #505 also records that clients using the SSE transport get Non-200 status code (410). For /mcp, the docs server, which needs no authentication, showed Connected, and the bindings server, which requires OAuth, showed Needs authentication.
Even with the URL still at /sse, the display changed when I added it with the transport set to http.
claude mcp add --scope local --transport http cf-docs-sse-as-http https://docs.mcp.cloudflare.com/sse
claude mcp list
cf-docs-sse-as-http: https://docs.mcp.cloudflare.com/sse (HTTP) - ✘ Failed to connect — HTTP 410: Error POSTing to endpoint: {"type":"https://developers.cloudflare.com/agents/model-context-protocol/cloudflare/servers-for-cloudflare/","title":"This MCP URL has moved to /mcp","status":410,"detail":"The [redacted] URL is no longer served. Update your MCP client configuration to https://docs.mcp.cloudflare.com/mcp.","url":"https://docs.mcp.cloudflare.com/mcp"}
Here the 410 body is displayed as is, so you can see the destination URL (the /sse in the body was replaced with [redacted] in Claude Code's display). The Changelog says that many MCP clients show the /mcp URL in their connection errors, but in Claude Code with a configuration whose transport is sse, only the status code was shown (I did not try clients other than Claude Code).
4. Switching the configuration to /mcp
First, find the configurations where a /sse URL remains. claude mcp list displays configurations regardless of scope (local, project, user), so starting here is the most reliable approach.
claude mcp list | grep 'mcp.cloudflare.com/sse'
cf-docs: https://docs.mcp.cloudflare.com/sse (SSE) - ✘ Failed to connect — HTTP 410: SSE error: Non-200 status code (410)
You can see which scope a found server is registered in from Scope in claude mcp get.
claude mcp get cf-docs
cf-docs:
Scope: Local config (private to you in this project)
Status: ✘ Failed to connect
Issue: HTTP 410: SSE error: Non-200 status code (410)
Type: sse
URL: https://docs.mcp.cloudflare.com/sse
Remove it by specifying the same scope, then add it again with the transport set to http (Streamable HTTP) and the URL set to /mcp. Replace the server name with the name in your own environment as shown by claude mcp list.
claude mcp remove cf-docs -s local
claude mcp add --scope local --transport http cf-docs https://docs.mcp.cloudflare.com/mcp
claude mcp list | grep cf-docs
cf-docs: https://docs.mcp.cloudflare.com/mcp (HTTP) - ✔ Connected
If it is written in a .mcp.json shared by your team (project scope), you will need to rewrite type and url in the file as follows and share it again. I did not verify a connection after this rewrite.
{
"mcpServers": {
"cf-docs": {
"type": "http",
"url": "https://docs.mcp.cloudflare.com/mcp"
}
}
}
I did not try clients other than Claude Code, but since the location of the configuration file differs by client, it looks like you will need to search each client's configuration file for mcp.cloudflare.com/sse.
Discussion of the results
- What was confirmed: all 17 servers listed in the README behaved the same way. The
/mcpURL to rewrite to can be determined mechanically from the response - How it appears in Claude Code: with a configuration whose transport is
sse,claude mcp listshows onlyNon-200 status code (410), and the destination URL does not appear. If you see a410, the most reliable approach is to check whether*.mcp.cloudflare.com/sseremains in your configuration - What was checked against official information: the Changelog's statement that "
/ssereturns 410" matched the curl results./mcpreturned 200 or 401 to an unauthenticatedinitialize, so it continues to respond. This method could not confirm that existing/mcpconnections are unaffected. The fact thatresource_metadatain the 401 responses points to/mcpis consistent with the PR's explanation that the OAuth resource was set to/mcp - Operational notes: if your team shares a
.mcp.json, you will need to rewrite both the URL and the transport and share it again
Summary
From October 22, 2026, Cloudflare's product-specific MCP servers offer only /mcp, and /sse returns 410 Gone along with the destination URL. All 17 servers I checked behaved this way.
In Claude Code, a configuration with the transport set to sse shows only Failed to connect and 410. If you find *.mcp.cloudflare.com/sse in claude mcp list, you can migrate by adding it again with the transport set to http and the URL set to /mcp, and, for servers that require OAuth, redoing the authorization.
I hope this is helpful to someone.
References:
