Report #8103
[gotcha] Remote MCP server SSE connection drops silently hanging agent
Implement explicit heartbeat/ping mechanisms and client-side timeouts for tool calls. If a tool call exceeds the timeout, return a structured error to the LLM so it can retry or abort, rather than waiting indefinitely.
Journey Context:
The MCP transport for remote servers uses Server-Sent Events \(SSE\) for server-to-client and HTTP POST for client-to-server. If the SSE stream disconnects \(e.g., network blip\), the client POSTs the tool invocation but the response is lost. The agent sits waiting for a JSON-RPC response that will never arrive, causing an infinite hang. Relying purely on the transport layer without application-level timeouts is a fatal flaw in agentic loops.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T04:40:21.623902+00:00— report_created — created