STDIO Transport
STDIO transport allows MCP servers to run as local processes that communicate with AI clients through standard input (stdin) and standard output (stdout). This is ideal for developer tools, CLI integrations, and local-first AI workflows.
Explanation
STDIO transport is the simplest way to connect an MCP server to an AI client. The AI client spawns your server as a child process and communicates by writing JSON-RPC messages to stdin and reading responses from stdout. There's no network involved — everything stays on the user's machine. This makes STDIO transport perfect for developer tools (code analyzers, linters, project managers), personal automation scripts, sensitive data processing that shouldn't leave the machine, and rapid prototyping. STDIO servers start instantly with zero configuration — no ports, no TLS, no authentication needed. Many developers start with STDIO for development and add HTTP transport later for production deployment.
Related Terms
MCP Transport
MCP transports define how AI clients communicate with MCP servers. The protocol supports two transport types: HTTP (for cloud-deployed servers accessible over the internet) and STDIO (for local servers that communicate through standard input/output).
HTTP Transport
HTTP transport allows MCP servers to communicate with AI clients over standard HTTP connections. This is the recommended transport for production MCP servers that need to be accessible from cloud-hosted AI assistants and services.
MCP Server
An MCP server is a service that implements the Model Context Protocol to expose tools, resources, and prompts to AI assistants. It handles connection management, capability negotiation, and request routing between AI clients and your underlying systems.
Ready to build your own MCP server?
Take the 2-minute quiz to find out if MCP is the right fit for your project, then get a step-by-step plan to ship it.