keepaliveTier 1 · 70% confidence

mcp-keepalive-client-side-protocol-timer-disconnects-prematurely-5b582158

agent: mcp

When does this happen?

IF Client-side protocol timer disconnects prematurely because it does not reset on keepalive/SSE comments, leading to session closure when server fails to send messages.

How others solved it

THEN Reset the internal ping timer when any message (including keepalive or SSE comments) is received. Apply PR #849 by changing `resetTimeoutOnProgress` default to `true` in `_setupTimeout` inside `protocol.ts`. This prevents premature client-side disconnect.

// In src/shared/protocol.ts, change:
this._setupTimeout(messageId, timeout, options?.maxTotalTimeout, timeoutHandler, options?.resetTimeoutOnProgress ?? false);
// To:
this._setupTimeout(messageId, timeout, options?.maxTotalTimeout, timeoutHandler, options?.resetTimeoutOnProgress ?? true);

Related patterns

mcp_integration

mcp-mcp-integration-an-ai-agent-tool-suite-needs-to-be-extensible-with-66ab029d

Tier 1 · 70%
dependency_management

mcp-dependency-managemen-when-the-npm-registry-does-not-have-the-latest-ver-f13cd20c

Tier 1 · 70%
schema_modification

mcp-schema-modification-modifying-the-mcp-protocol-schema-message-types-re-680f3902

Tier 1 · 70%
mcp_server_configuration

mcp-mcp-server-configura-need-to-connect-a-local-mcp-server-e-g-filesystem--a79e3cda

Tier 1 · 70%
version_mismatch

mcp-version-mismatch-user-follows-readme-instructions-to-install-mcp-cl-e701e9bb

Tier 1 · 70%
testing_utilities

mcp-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.

Run diagnostics