You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
McpError: MCP error -32001: Request timed out #8478
I have a question regarding an issue I encountered while using Gemini 3 Pro with MCP. When Opencode was waiting for an MCP response, the TUI threw the following error: McpError: MCP error -32001: Request timed out.
The AI also informed me that the MCP timed out; it appears that because the MCP was actively running a task, it failed to respond to Opencode. Consequently, I suspect that Opencode's default timeout duration is too short.
Could anyone advise on which setting or variable I should modify to extend the wait time? Or could there be another reason for this?
Both issues describe the same problem: MCP error -32001 (request timeout) occurring when MCP tools take longer than expected to execute, and both ask about configuring or extending the timeout duration.
Feel free to ignore if this doesn't address your specific case.
This worked for me in addressing the unexpectedly-short ("McpError: MCP error -32001: Request timed out") timeout issue. (I set my timeout here to 10 minutes)
Activity
github-actions commentedon Jan 14, 2026
This issue might be a duplicate of existing issues. Please check:
Both issues describe the same problem: MCP error -32001 (request timeout) occurring when MCP tools take longer than expected to execute, and both ask about configuring or extending the timeout duration.
Feel free to ignore if this doesn't address your specific case.
cravenceiling commentedon Jan 14, 2026
Try adding this
mcp_timeoutexperimental property to your config file:By the way, that error seems to come from the mcp server itself, or at least I couldn't find it in the codebase.
sohowillycow commentedon Jan 14, 2026
May I ask what the time unit is? What is the maximum value that can be set? Thank you very much for your answer.
cravenceiling commentedon Jan 14, 2026
Sure, it's in milliseconds (ms), and if I'm not wrong, the maximum is
9007199254740991.sohowillycow commentedon Jan 14, 2026
Thank you very much. I will test it out later.
tylerburleigh commentedon Jan 19, 2026
This worked for me in addressing the unexpectedly-short ("McpError: MCP error -32001: Request timed out") timeout issue. (I set my timeout here to 10 minutes)
github-actions commentedon Mar 26, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.