Stdio transport exchanges structured messages through standard input and standard output. In a local MCP integration, a client launches the server as a separate Node.js process and communicates without exposing HTTP endpoints. section 12.3.2
A typical request flow is:
- The MCP client discovers the server's tools and makes them available to an AI model or LangChain agent. section 12.3.2 section 12.5.2
- The server executes tool logic, such as an external API request, and returns structured MCP-compliant content through stdio. section 12.3.2
- The transport keeps external API access inside the MCP server, separating it from the model. section 12.3.2
Local joke tool
A Next.js chat application launches a local MCP server over stdio. The server exposes get-chuck-joke, calls api.chucknorris.io, and returns the result; the model accesses only the exposed tool. section 12.3.2


