Repository navigation
[Feature Request] Make MCP server call timeout configurable for long-running operations #24532
Closed as not planned
Description
Activity
Found 3 possible duplicate issues:
- [FEATURE] Make MCP Tool Execution Timeout Configurable in Claude Desktop #22542
- [BUG] Claude code does not obey values of MCP_TIMEOUT longer than 60 seconds #16837
- [Bug] MCP_TOOL_TIMEOUT not respected for long-running HTTP tool calls #17662
This issue will be automatically closed as a duplicate in 3 days.
- If your issue is a duplicate, please close it and 👍 the existing issue instead
- To prevent auto-closure, add a comment or 👎 this comment
🤖 Generated with Claude Code
Reacted by AmirClosing for now — inactive for too long. Please open a new issue if this is still relevant.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
- locked as resolved and limited conversation to collaborators
on Mar 19, 2026
Bug Description
please make the hardcoded 45 minutes for mcp call timeout customizable. i run circuit simulations that can take hours but limits of claude code stops from running long simulations.
Environment Info
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/specialpedrito/.local/share/claude/versions/2.1.37 (expected in multi-process scenarios)\n at fq$ (/$bunfs/root/claude:3581:2098)\n at rjA (/$bunfs/root/claude:3581:1209)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-09T22:02:19.293Z"}]