sse_connection_handlingTier 1 · 70% confidence
mcp-sse-connection-handl-sse-connection-drops-with-body-timeout-error-after-67ccf2c8
agent: mcp
When does this happen?
IF SSE connection drops with 'Body Timeout Error' after ~300 seconds of inactivity when using MCP SSE server in Cursor.
How others solved it
THEN Implement a keep-alive mechanism by periodically writing an SSE comment to the response stream. For example, set an interval (e.g., every 25 seconds) to write ': keepalive\n\n' to the response object. This prevents the connection from being terminated due to inactivity.
const KEEP_ALIVE_INTERVAL_MS = 25000;
const sseConnections = new Map();
app.get('/sse', async (req, res) => {
const transport = new SSEServerTransport('/messages', res);
const intervalId = setInterval(() => {
res.write(': keepalive\n\n');
}, KEEP_ALIVE_INTERVAL_MS);
// Store interval for cleanup
});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.