Skip to content
AdminKit

stdio transport (MCP)

What is stdio transport (MCP)?

The stdio transport is one of MCP's two standard transports, letting a client spawn an MCP server as a local child process and exchange JSON-RPC messages over its standard input and output instead of a network socket. AdminKit's own adminkit-mcp connector defaults to stdio for local use.

By AdminKit team, Netbase JSC · Updated

The stdio transport is one of the ways a Model Context Protocol client and server exchange JSON-RPC messages, using the server process’s standard input and standard output streams instead of a network socket. The client spawns the MCP server as a local child process, writes requests to its stdin, and reads responses from its stdout, which works well for a server running on the same machine as the client — a desktop AI application or IDE integration launching a local tool server, for example — but can’t be used for a server on a different machine, since no network transport is involved at all. The specification has each message delimited by a newline and lets the server write log output to stderr, the third of the standard I/O streams POSIX defines alongside stdin and stdout. That same local desktop scenario is also the common case for roots, where the client advertises which directories its locally-spawned server’s tools should stay within. MCP’s other current transport, Streamable HTTP, replaced an older SSE-based transport and is used instead whenever the client and server aren’t on the same host. AdminKit’s own adminkit-mcp connector defaults to stdio, with an —http flag available when a remote client needs network access instead.

AdminKit groups stdio transport (MCP) under its AI agents & MCP cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

How does the stdio transport exchange messages?

Over the MCP server process's standard input and standard output streams, instead of a network socket.

Can the stdio transport reach a server on a different machine?

No -- the client spawns the MCP server as a local child process, so stdio only works when client and server share the same machine.

What transport replaces stdio for a remote MCP server?

Streamable HTTP, which replaced an older SSE-based transport for networked servers.

What does AdminKit's own MCP connector default to?

stdio, for local use, with an --http flag available when a remote client needs network access instead.