[ ABORT TO HUD ]
SEQ. 1
SEQ. 2
SEQ. 3

The Stdio Transport

🚄 Transport Layers6 min60 BASE XP

Local Communication via Stdio

The stdio (Standard Input/Output) transport is the most common way to run MCP servers locally. It is lightweight, extremely secure, and requires no open network ports.

How it Works

The Host application (like Claude Desktop) launches the MCP Server as a child subprocess. It communicates by writing JSON-RPC messages to the server's stdin and reading from its stdout.

{
  "mcpServers": {
    "local-db": {
      "command": "node",
      "args": ["/path/to/server.js"],
      "env": { "DB_PASS": "secret123" }
    }
  }
}
🎯 Pro Tip: When using the stdio transport, your server code must never log debug information using console.log(), because it will corrupt the JSON-RPC stream on stdout! Use console.error() for debug logging instead.
SYNAPSE VERIFICATION
QUERY 1 // 3
Why is the stdio transport considered extremely secure?
It uses 256-bit AES encryption.
It runs entirely locally as a child process without opening any network ports.
It requires an internet connection to Anthropic servers.
It requires a biometric hardware key.
Watch: 139x Rust Speedup
The Stdio Transport | Transport Layers — MCP Academy