Streamable HTTP transport (MCP)
What is Streamable HTTP transport (MCP)?
Streamable HTTP is the MCP transport for a networked server, letting a client connect over ordinary HTTP request and response bodies instead of a locally spawned process; it replaced an earlier HTTP-plus-SSE transport. AdminKit's adminkit-mcp connector supports it via an --http flag for remote agents.
By AdminKit team, Netbase JSC · Updated
Streamable HTTP is one of the two transports the Model Context Protocol specification defines for how a client and server exchange its JSON-RPC messages, the other being stdio. Where stdio requires the client to spawn the server as a local child process and talk over its standard input and output, Streamable HTTP lets the server run as a standalone, long-lived HTTP service that a client connects to over the network — the transport a remote or hosted MCP server needs, since stdio has no concept of a different machine at all. It replaced an earlier HTTP-plus-SSE transport in the MCP specification. SSE didn’t disappear entirely: a Streamable HTTP server may answer a client’s POST with a text/event-stream response, using the server-sent events format from the WHATWG HTML standard, to stream several messages back instead of a single JSON object. AdminKit’s own adminkit-mcp connector defaults to stdio but supports an —http flag (adminkit-mcp —http :8080) to serve Streamable HTTP instead, for exactly the case where a remote agent, rather than a locally spawned one, needs to connect. Either transport can carry a progress notification back to the client for a long-running call, since both ultimately exchange the same JSON-RPC messages regardless of which one moves the bytes.
AdminKit groups streamable HTTP transport (MCP) under its AI agents & MCP cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
What problem does Streamable HTTP solve that stdio cannot?
It lets an MCP server run as a standalone, long-lived HTTP service a client connects to over the network, which stdio cannot do since it requires a locally spawned process.
What transport did Streamable HTTP replace?
An earlier HTTP-plus-SSE transport in the MCP specification.
How does AdminKit's own connector expose Streamable HTTP?
Via an --http flag, for example adminkit-mcp --http :8080, alongside its stdio default.
Do stdio and Streamable HTTP carry the same message format?
Yes -- both ultimately exchange the same JSON-RPC messages, just over different channels.