# /sse changes: it no longer serves the HTTP+SSE transport

Calls to /sse on Cloudflare Ai Gateway MCP stopped working on July 28, 2026.

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.

## What to use instead

Connect to /mcp over Streamable HTTP, or configure your client to detect the transport automatically.

- 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
- Calls it hits: `/sse`
- Source: [Announcement](https://developers.cloudflare.com/changelog/post/2026-07-28-cloudflare-mcp-servers-mcp-2026-07-28/)
- Verified: November 6, 2026, against Cloudflare Ai Gateway MCP's own pages
- Page: https://www.okapi.bot/providers/cloudflare-ai-gateway-mcp/breaking-changes/sse-changes-it-no-longer-serves-the-http-sse-transport/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent