{"version":"2.1.187","anchor":"mcp-tool-idle-timeout-detection","canonical_anchor":"mcp-tool-idle-timeout-detection","heading":"MCP tool idle timeout detection","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.187\/e\/mcp-tool-idle-timeout-detection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.187","markdown":"### MCP tool idle timeout detection\n\n**What**\n\nMCP tools that stop sending progress or responses are now detected and aborted after a configurable timeout. A new env var controls the timeout duration.\n\n**Usage**\n\n`# Set timeout in milliseconds (default is built-in; 0 disables timeout) export CLAUDE_CODE_MCP_TOOL_IDLE_TIMEOUT=120000 # 2 minutes export CLAUDE_CODE_MCP_TOOL_IDLE_TIMEOUT=0 # disable` **Details** - When an MCP tool produces no output for the configured duration, Claude aborts the call and reports the timeout - Error message includes the tool name and duration: \"MCP server `X` tool `Y` sent no response or progress for Ns; aborting\" - A new `McpResponseSchemaError` is thrown and surfaced when an MCP server returns a result that fails schema validation, with a description of what was wrong **Evidence** New timeout guard (search for `\"CLAUDE_CODE_MCP_TOOL_IDLE_TIMEOUT\"` or `\"MCP tool idle timeout\"`)"}