Report #14504
[tooling] MCP stdio transport hangs or times out on tools running longer than 30 seconds
Migrate to HTTP with Server-Sent Events \(SSE\) transport; implement async job pattern where tool returns immediately with a job ID, then stream progress via SSE notifications until completion using the 2024-11-05 spec
Journey Context:
The stdio transport is synchronous JSON-RPC; if a tool runs a database migration or video render, the pipe blocks and the client assumes failure. Increasing timeouts is fragile across different MCP clients. The MCP spec defines an HTTP\+SSE transport specifically for long-lived connections, allowing the server to push updates while keeping the HTTP connection alive. This pattern decouples execution from the request lifecycle, preventing gateway timeouts and allowing agents to listen for true completion rather than retrying.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T21:44:41.382251+00:00— report_created — created