What
MCP_TOOL_TIMEOUT is now read through the central environment reader rather than parsed inline, and two new environment variables control how many MCP servers are connected at once: MCP_SERVER_CONNECTION_BATCH_SIZE (default 3) and MCP_REMOTE_SERVER_CONNECTION_BATCH_SIZE (default 20).
Details
- The old inline parse required a value greater than zero; both tool-timeout helpers now share the one source.
- Raise the remote batch size if you have many remote MCP servers and startup connection is slow.
Usage
MCP_REMOTE_SERVER_CONNECTION_BATCH_SIZE=40 claudeEvidence
MCP_REMOTE_SERVER_CONNECTION_BATCH_SIZE
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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 MCP_TOOL_TIMEOUT, on Code in Claude Desktop on 3P.
| `mcpToolTimeoutSec` | Applies your per-call MCP tool timeout to Code sessions as well, taking precedence over a user-set `MCP_TOOL_TIMEOUT`. |third-party/claude-desktop/code see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up MCP_TOOL_TIMEOUT, on Code in Claude Desktop on 3P.