Streamable HTTP
The MCP transport for servers reached over a network: every client message is an HTTP POST to one endpoint, and the server answers with a JSON body or a server-sent events stream.
MCP messages are JSON-RPC. A transport decides how they travel. With stdiostdio transport: The MCP transport in which the client starts the server as a child process and exchanges newline-delimited JSON-RPC messages over the process's standard input and output. the client starts the server itself; with Streamable HTTP the server is an independent process that many clients can reach at one URL, such as https://example.com/mcp. It replaced the older HTTP+SSE transport from the 2024-11-05 revision, which needed two endpoints.
How it works in the 2025-11-25 revision:
- One endpoint. The client POSTs each message and must accept both
application/jsonandtext/event-stream. For a request, the server picks: one JSON object, or an SSE stream that can carry progress notifications before the response. - Optional GET. A client may open an SSE stream with GET to hear from the server unprompted. A server that offers none answers 405.
- Sessions. A server may return an
MCP-Session-Idheader with itsinitializereply. The client then sends it on every request; a 404 means the session is gone and the client must initialize again. DELETE ends it. - Version header. Every later request carries
MCP-Protocol-Version. - Origin checks. Servers must validate the
Originheader and answer 403 when it is invalid, because DNS rebinding can let a web page reach a local server.
Example
POST /mcp HTTP/1.1
Accept: application/json, text/event-stream
MCP-Session-Id: 1868a90c
MCP-Protocol-Version: 2025-11-25
{"jsonrpc":"2.0","id":7,"method":"tools/call","params":{"name":"search","arguments":{"q":"refund"}}}Common confusion
Streamable HTTP is not "MCP over SSE". SSE is only one way a reply can come back, and many replies are plain JSON. Note too that the 2026-07-28 revision drops the initialize handshake and its connection-scoped session: each request carries its protocol version and capabilities in the message body. By default L2M's gateway speaks 2025-11-25, 2025-06-18 and 2025-03-26, and serving 2026-07-28 is opt-in. As a client, L2M asks for 2025-06-18 and switches to 2026-07-28 only for a server that speaks nothing older.
In L2M
L2M's http_mcp adapter connects to remote servers over Streamable HTTP only, not the old HTTP+SSE transport. In the other direction, each toolsetToolset: A named, curated group of tools, drawn from several MCP servers and workflows, served at one MCP endpoint so each client sees only the tools it needs. on the MCP gateway is a Streamable HTTP endpoint of its own, POST /mcp/<slug>, which checks Origin and can stream progress as SSE. The opt-in for 2026-07-28 clients is MCP_GATEWAY_MODERN_PROTOCOL=on.
Further reading
- MCP specification 2025-11-25: transports (modelcontextprotocol.io)
- MCP specification 2026-07-28: transports overview (modelcontextprotocol.io)