Claude Code / AI Coding Tools

Claude Code MCP_TOOL_TIMEOUT Ignored — HTTP Transport Hardcodes 60s Timeout

Fix Claude Code MCP_TOOL_TIMEOUT environment variable being ignored for HTTP MCP servers Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 13, 2026 2 sources Needs local verification

Category: AI Coding Tools
Error signature: MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 13, 2026
Verification status: Source-backed
Evidence: 2 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Claude Code, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls is a Claude Code failure pattern reported for developers trying to fix claude code mcp_tool_timeout environment variable being ignored for http mcp servers. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Claude Code 2.1.5+ hardcodes 60s AbortSignal.timeout() on HTTP fetch, ignoring MCP_TOOL_TIMEOUT env var. Long-running MCP tools return empty {} silently. Multiple issues filed, fix needed for version 2.1.113+.

Common causes

HTTP MCP tool calls silently timeout at 60s despite MCP_TOOL_TIMEOUT being set, returning empty {} responses with no error — impossible to debug long-running tools
Claude Code 2.1.5+ hardcodes 60s AbortSignal.timeout() on HTTP fetch, ignoring MCP_TOOL_TIMEOUT env var. Long-running MCP tools return empty {} silently. Multiple issues filed, fix needed for version 2.1.113+.

Quick fixes

Confirm the exact error signature matches MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls.
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls exactly before applying the quick fix.
Compare the failing environment with Claude Code versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls mean in Claude Code?

MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls indicates the workflow described by "Claude Code MCP_TOOL_TIMEOUT Ignored — HTTP Transport Hardcodes 60s Timeout" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls?

Check whether this cause matches your environment: HTTP MCP tool calls silently timeout at 60s despite MCP_TOOL_TIMEOUT being set, returning empty {} responses with no error — impossible to debug long-running tools

Is the MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls guidance source-backed?

The "Claude Code MCP_TOOL_TIMEOUT Ignored — HTTP Transport Hardcodes 60s Timeout" page is labeled source-backed. It has 2 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls?

For "Claude Code MCP_TOOL_TIMEOUT Ignored — HTTP Transport Hardcodes 60s Timeout", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging MCP_TOOL_TIMEOUT not respected for HTTP MCP tool calls?

For "Claude Code MCP_TOOL_TIMEOUT Ignored — HTTP Transport Hardcodes 60s Timeout", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.