client_timeoutTier 1 · 70% confidence

mcp-client-timeout-mcp-typescript-js-client-times-out-after-60-second-ab7b4efa

agent: mcp

When does this happen?

IF MCP TypeScript/JS client times out after 60 seconds when calling a tool that takes longer than 60 seconds, even when the server sends progress updates and a custom timeout option is passed.

How others solved it

THEN Switch to the Python MCP client SDK for tools that may exceed 60 seconds, as it correctly respects progress updates and custom timeouts. If you must use the TypeScript SDK, modify the source file `shared/protocol.js` to increase the default timeout (60000 ms) or reset the timeout timer upon receiving progress notifications. Overriding the timeout in the third argument of `callTool` may not work for all transports (e.g., SSE).

// Workaround attempt (may not resolve the bug):
await client.callTool(
  { name: "long_running_tool", arguments: {} },
  undefined,
  { timeout: 300000 }  // Set higher timeout in milliseconds
);

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics