Timeout Configuration / Claude Code v1.0.8

Configurable MCP timeouts via environment variables:
MCP_TIMEOUT: General MCP operation timeout (default: 30 seconds)
MCP_TOOL_TIMEOUT: MCP tool execution timeout (default: 100 seconds)

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed edge cases where MCP_TIMEOUT and MCP_TOOL_TIMEOUT weren't being respected

See this entry in the whole of v1.0.8 →

The build it came inv1.0.8

2 Jun 2025 · 12 entries, this one is #8.

Either side of it

v1.0.7Older
v1.0.9Newer

Open the release →

Names in this entry

envMCP_TIMEOUT
Very large MCP_TIMEOUT values are capped instead of overflowing and timing out instantly.
envMCP_TOOL_TIMEOUT
Two new env vars set how many MCP servers connect at once, local and remote.

Anthropic's note

Upstream's own release notes for v1.0.8 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed edge cases where MCP_TIMEOUT and MCP_TOOL_TIMEOUT weren't being respected

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.