Streamable HTTP transport (MCP)
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. 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.
By AdminKit team, Netbase JSC · Updated