MCP Directory
MCP Glossary

stdio transport

Definition
stdio transport runs an MCP server as a local process and communicates with it over standard input/output — no network involved.

It's the default and the most common transport: about 90% of servers in this directory are stdio. The server launches via npx, uvx, node or docker on your machine, reads requests on stdin and writes responses on stdout. The big advantage is privacy and simplicity — nothing leaves your computer, and there's no endpoint to host. The catch: it can't be shared across a team.

FAQ

Is stdio or remote MCP better?

For a single developer on one machine, stdio is simpler and more private and is the right default. Choose remote (HTTP/SSE) only when you need to share a setup or rely on heavy hosted infrastructure.