Skip to content
BENIBIX Learn

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.

AI⌨️ Claude Code

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.

Example
Lucy's MCP server downloads a model when it starts and takes 45 seconds. She sets the wait to a minute, and its tools show up.
Why it matters
A slow server that misses the wait looks broken, even though it works.
Full entry
AI⌨️ Claude Code

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.

Example
Jack's HTTP server runs reports that take 2 minutes, and they kept failing at 60 seconds. He sets 5 minutes, and the reports come back.
Why it matters
Slow tools on a web server hit the 60 second wall unless you raise it.
Full entry

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.