Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.260 ·

New admin config key: mcpToolTimeoutSec caps MCP tool call duration

Admins can now cap how long MCP tool calls are allowed to run.

Use it now Notable New Features
JSON All of v2.1.260
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
New FeaturesKind: in v2.1.260,
What probably matters to youSection of the release

A new managed-config field, mcpToolTimeoutSec, lets an org set a per-call timeout of 60-3600 seconds for MCP tool calls. Cowork/chat already defaulted to 180s, but Code sessions previously had no desktop-imposed MCP timeout; setting this key now gives them one, and the desktop's own request deadlines toward managed and user-added local MCP servers follow this value.

Read from
Names in the bundlemcpToolTimeoutSec
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up mcpToolTimeoutSec, on Configuration reference. | <span id="mcptooltimeoutsec" />MCP tool call timeout<br />`mcpToolTimeoutSec` | `integer` | MDM + Bootstrap<br />Added in 1.37937.0 | — | Per-call timeout for MCP tool calls, in seconds. Default 180 (3 minutes). Range: 60–3600. | third-party/claude-desktop/configuration see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up mcpToolTimeoutSec, on Configuration reference.

See this entry in the whole of v2.1.260 →

Feedback