fix: resetTimeoutOnProgress does nothing without onprogress callback

[malventano]

Refs #2076.

There's a setting in the MCP client library that keeps long-running tasks from timing out. By default, requests die after 60 seconds. With this setting turned on, every time the server reports "I'm still working," that 60-second timer resets so the task can continue. But it only works if the client also provides an onprogress callback alongside it. If the client passes resetTimeoutOnProgress: true without also passing onprogress, the progress notifications arrive but are silently dropped and the timer never resets. The option claims to work on its own — it doesn't.

Why it happens

_onprogress() looks up the handler in _progressHandlers first, and that map is only populated when onprogress is provided (in request()). If no handler exists, the method errors and returns before reaching the timeout reset code.

The fix

Move the timeout reset before the handler lookup. Guard only handler(params).

After

• resetTimeoutOnProgress: true works standalone — no onprogress needed
• Existing callers with both options work identically
• Unknown tokens still error after attempted reset

[changeset-bot]

⚠️ No Changeset found

Latest commit: dd05570

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@modelcontextprotocol/sdk@2136

commit: dd05570