Streamable HTTP vs SSE transport

The 2025-03-26 Streamable HTTP transport replaced the legacy HTTP+SSE transport — here's what actually changed.

⚖️ Our verdict
Always prefer Streamable HTTP. Keep SSE URLs only for clients pinned to the 2024 spec — and bridge them with mcp-remote when your client is HTTP-only.

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.

Frequently Asked Questions

Does Streamable HTTP still use SSE?
Optionally — the server may stream progress notifications as SSE frames inside a POST response. Clients that don't need streaming get plain JSON.
My client only has SSE. Now what?
Use mcp-remote: `npx -y mcp-remote <streamable-url>` exposes the remote endpoint over local stdio and handles transport translation.