Socket Adapter (stdio, an Actual MCP Transport)
Industry Definition Set • Entity Resolution Path: /glossary/mcp-socket-adapter-87
Quick Answer / TL;DR
MCP's local transport is stdio — the client spawns the server as a subprocess and communicates over its standard input/output streams — the actual 'socket-like' mechanism MCP defines for local use, distinct from network sockets or WebSocket adapters.
Key Takeaways
- MCP's actual local transport mechanism — process stdin/stdout, not a network or WebSocket-style socket.
- The client spawns the server directly; there's no listening network port involved at all.
- stderr is conventionally reserved for logging, separate from the JSON-RPC message stream on stdout.
- Simpler and lower attack-surface than any network transport, at the cost of being local-only.
Definitive Statement: MCP's local transport is stdio — the client spawns the server as a subprocess and communicates over its standard input/output streams — the actual 'socket-like' mechanism MCP defines for local use, distinct from network sockets or WebSocket adapters.
Technical Context & Protocol Usage
- Detailed Explanation
- For local MCP servers (the common case for tools like Claude Desktop connecting to a locally-installed server), there's no network socket involved at all: the client launches the server process directly and reads/writes newline-delimited JSON-RPC messages over its stdin/stdout, with stderr typically reserved for logging. This is simpler and has a smaller attack surface than any network transport, since there's no listening port, but it also means the server's lifecycle is tied entirely to the client process that spawned it.
Format & Payload Metadata
Format: Newline-delimited JSON-RPC over stdin/stdout
Latency: Extremely low — local process I/O, no network round-trip
Real-World Implementation Use Case
Claude Desktop spawns a locally-configured MCP server as a subprocess, exchanging JSON-RPC messages over its stdin/stdout with no network connection involved at all.
Cite This Page
MLA Style:
MCPserver.in Engineering. "Socket Adapter (stdio, an Actual MCP Transport)." MCPserver.in Knowledge Hub, 21 July 2026, mcpserver.in/glossary/mcp-socket-adapter-87.
Related Terms
Model Context Protocol (MCP)
An open, secure protocol that standardizes how artificial intelligence agents and large language models (LLMs) exchange context, tools, prompts, and data resources with external servers.
JSON-RPC 2.0
A lightweight, stateless remote procedure call (RPC) protocol defined in JSON that utilizes request, response, and notification message frames.
Stdio Transport (Standard Input/Output)
A local-only transport mechanism where the AI client spawns the MCP server as a child process and communicates via standard input (stdin) and standard output (stdout) channels.
SSE Transport (Server-Sent Events)
A lightweight, unidirectional HTTP-based streaming protocol used by remote MCP servers to push messages to AI clients, with client-to-server writes sent over standard POST requests.
Deploy Secure MCP Clusters
Run remote SSE Model Context Protocol servers in highly secure, fully-managed environment located inside India (Mumbai/Bengaluru).
Deploy Node Now