Report #16480
[tooling] MCP local server connection timeout using HTTP transport
Use stdio transport for local MCP servers instead of SSE/HTTP to eliminate port conflicts, CORS issues, and process lifecycle management complexity.
Journey Context:
Developers default to HTTP/SSE because it feels 'standard,' but local MCP servers run as child processes. Using HTTP requires managing ports, handling firewall prompts, and implementing health checks. stdio uses process pipes for communication; the host spawns the process, owns its lifecycle, and communicates via stdin/stdout with lower latency. This is the transport designed for local execution in the MCP specification.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T02:47:12.524962+00:00— report_created — created