Cloudflare Ai Gateway MCP
/sse changes: it no longer serves the HTTP+SSE transport
Stopped workingSubscribe to Cloudflare Ai Gateway MCPShare
On July 28, 2026, the /sse endpoint stopped serving the HTTP+SSE transport. The path remains an alias for the Streamable HTTP handler, but any calls that explicitly force the SSE transport now fail.
Calls it hits
/sse
What to use instead of these calls
Connect to /mcp over Streamable HTTP, or configure your client to detect the transport automatically.
In Cloudflare Ai Gateway MCP's words
Historical /sse URLs continue to work as aliases for the same Streamable HTTP handler, but they no longer serve the deprecated HTTP+SSE transport. If a client forces SSE transport, change it to Streamable HTTP or automatic transport detection.
Facts
- API
- Cloudflare Ai Gateway MCP
ai-gateway.mcp.cloudflare.com - Kind
- Behaviour change
- Announced
- July 28, 2026
- Takes effect
- July 28, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Cloudflare Ai Gateway MCP's own pages
Questions
When does this change take effect?
Calls to /sse on Cloudflare Ai Gateway MCP stopped working on July 28, 2026.
What happens to calls after July 28, 2026?
They have failed since July 28, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.