Streamable HTTP vs SSE transport
The 2025-03-26 Streamable HTTP transport replaced the legacy HTTP+SSE transport — here's what actually changed.
Two endpoints vs one
Legacy SSE required two endpoints: POST /messages for requests and GET /sse for a persistent event stream. Streamable HTTP collapses everything into a single endpoint that can stream SSE frames inside a normal POST response when needed.
Session handling
SSE tied sessions to the long-lived GET connection. Streamable HTTP introduces the Mcp-Session-Id header, making sessions explicit, resumable and load-balancer friendly.
Serverless compatibility
Legacy SSE was painful on Workers/Lambda because of the held-open GET stream. Streamable HTTP works fine stateless — a server can answer each POST with plain JSON and skip SSE entirely.
Client support
Every modern client (Cursor, Claude Code, VS Code, ChatGPT, Codex, Gemini) defaults to Streamable HTTP. SSE survives only for backwards compatibility with older servers.