HTTP+SSE vs Streamable HTTP
People think Streamable HTTP got rid of streams, since the old MCP transport it replaced was named after them. It did not. The old HTTP+SSE transport needed two addresses: one long stream to listen and one to send. Streamable HTTP uses one address. A reply can still come back as a stream when it needs to. The change was fewer addresses, not fewer streams.
HTTP+SSE Transport
The old way to reach a remote MCP server. It used two web addresses.
The HTTP+SSE transport is the old way to reach a remote MCP server, from the 2024-11-05 release. The client opened one long stream to hear the server, using server-sent events. It sent its own messages to a second address. It was marked old in 2025-03-26, when Streamable HTTP took its place. New servers should not use it, though some clients still speak it so older servers keep working.
Streamable HTTP Transport
An MCP link to a server on the web. It uses HTTP requests.
The Streamable HTTP transport lets a client reach an MCP server over a network, such as the internet. The client sends each message to one web address with an HTTP request. The server can send back one reply or stream several messages back as events. One server can serve many users at once. It replaced an older HTTP transport in 2025, and it is now the standard way to run remote servers.
In one line
- HTTP+SSE Transport
- The old way to reach a remote MCP server. It used two web addresses.
- Streamable HTTP Transport
- An MCP link to a server on the web. It uses HTTP requests.