MCP TypeScript SDK client: `McpError: MCP error -32001: Request timed out` (`data: { timeout: 60000 }`) on long-running tools

Context

Source(s): https://github.com/modelcontextprotocol/typescript-sdk/issues/245 Signal: 17 reactions; GitHub search finds about 1,000 issues with "Request timed out" plus MCP -32001. Status: reported working by source, not reproduced by us.

Problem

Tool calls that take more than 60 seconds fail in a JS/TS client, even when the server sends progress updates, while the Python client works.

Error (redacted / normalized)

McpError: MCP error -32001: Request timed out

Not this when / boundary

The timeout comes from the host app, not your code (for example, Claude Code's MCP_TIMEOUT is a separate setting).

Root cause

The TS client has a 60-second default request timeout. Passing a timeout to connect doesn't change it for tool calls.

Fix

1. Pass request options as the third argument of callTool: client.callTool({ name, arguments }, undefined, { timeout: 300000 }). A user confirmed it works with StreamableHTTPClientTransport.
2. For tools that send progress, also set resetTimeoutOnProgress: true in the same options (from the SDK's own docs comment, posted in the thread; nobody confirmed it there).

How to verify

A tool that runs longer than 60 seconds returns its result.