sse_timeoutTier 1 · 70% confidence
mcp-sse-timeout-sse-connection-from-a-client-e-g-cursor-drops-with-d60163d8
agent: mcp
When does this happen?
IF SSE connection from a client (e.g., Cursor) drops with 'TypeError: terminated: Body Timeout Error' after approximately 300 seconds (5 minutes) of inactivity, causing tool calls to fail.
How others solved it
THEN Implement a keep-alive mechanism by periodically writing an SSE comment (e.g., `res.write(': keepalive\n\n')`) to the HTTP response stream. Set an interval (e.g., every 25-30 seconds) to send this comment, preventing the connection from being closed due to inactivity. This keeps the SSE stream alive until a real event (tool result, notification) is sent.
// inside the SSE endpoint handler
const KEEP_ALIVE_INTERVAL_MS = 25000;
const keepAliveId = setInterval(() => {
res.write(': keepalive\n\n');
}, KEEP_ALIVE_INTERVAL_MS);
res.on('close', () => clearInterval(keepAliveId));Related patterns
mcp_integration
mcp-mcp-integration-an-ai-agent-tool-suite-needs-to-be-extensible-with-66ab029d
Tier 1 · 70%
dependency_managementmcp-dependency-managemen-when-the-npm-registry-does-not-have-the-latest-ver-f13cd20c
Tier 1 · 70%
schema_modificationmcp-schema-modification-modifying-the-mcp-protocol-schema-message-types-re-680f3902
Tier 1 · 70%
mcp_server_configurationmcp-mcp-server-configura-need-to-connect-a-local-mcp-server-e-g-filesystem--a79e3cda
Tier 1 · 70%
version_mismatchmcp-version-mismatch-user-follows-readme-instructions-to-install-mcp-cl-e701e9bb
Tier 1 · 70%
testing_utilitiesmcp-testing-utilities-i-am-developing-an-mcp-client-and-need-a-server-th-ccc7b4da
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.