MCP_TIMEOUT vs MCP_TOOL_TIMEOUT
People think MCP_TIMEOUT is the limit on how long an MCP tool can run. It is the wait for a server to start, 30 seconds by default. MCP_TOOL_TIMEOUT is the limit on one tool call, about 28 hours by default, with a 60 second limit per request on servers reached over HTTP. A server that never shows its tools needs the first. A tool that fails partway needs the second.
MCP_TIMEOUT
It sets how long Claude Code waits for an MCP server to start.
MCP_TIMEOUT sets how long Claude Code waits for an MCP server to start. The value is in milliseconds. The default is 30,000, which is 30 seconds. A server that takes longer is not ready when the session begins.
MCP_TOOL_TIMEOUT
It sets how long one MCP tool call may run.
MCP_TOOL_TIMEOUT sets how long one MCP tool call may run before Claude Code stops it. The value is in milliseconds, and the default is about 28 hours. A server reached over HTTP also stops each request after 60 seconds. Set this above 60,000 to raise that too. A timeout set for one server in .mcp.json wins for that server.
In one line
- MCP_TIMEOUT
- It sets how long Claude Code waits for an MCP server to start.
- MCP_TOOL_TIMEOUT
- It sets how long one MCP tool call may run.