Stdio
A built-in local communication mechanism in MCP that enables inter-process communication via standard input and output streams, suitable for local tool invocation scenarios.
Core Facts
MCP has a built-in Stdio (standard input/output) local communication mechanism, but Stdio cannot transmit across networks and can only be used for inter-process communication on a local machine.
STDIO mode can only be used for communication on the same machine and cannot be deployed across networks.
In the Stdio communication method, data is transferred between parent and child processes via stdin and stdout pipes without going through the network stack, and latency can be as low as the microsecond level.
Timeline (last 90 days)
The Stdio (standard input/output) transport protocol requires no network configuration and works out of the box, but is bound to the process lifecycle, making it suitable for local testing and unable to scale horizontally.
MCP has a built-in Stdio (standard input/output) local communication mechanism, but Stdio cannot transmit across networks and can only be used for inter-process communication on a local machine.
All Facts (4)
MCP has a built-in Stdio (standard input/output) local communication mechanism, but Stdio cannot transmit across networks and can only be used for inter-process communication on a local machine.
80%VerifiedSTDIO mode can only be used for communication on the same machine and cannot be deployed across networks.
65%VerifiedIn the Stdio communication method, data is transferred between parent and child processes via stdin and stdout pipes without going through the network stack, and latency can be as low as the microsecond level.
65%UnverifiedThe Stdio (standard input/output) transport protocol requires no network configuration and works out of the box, but is bound to the process lifecycle, making it suitable for local testing and unable to scale horizontally.
50%