I am trying to run yarn commands in a project (e.g. in this case generating graphql types). The command takes let’s say a minute to execute.
Cursor reports that there is a timeout and doesn’t wait for the command to complete.
Can this timeout for the tools of an MCP server be made configurable?
Currently there’s no way to configure the timeout for MCP server tools.
However, to quote @msfeldstein when I asked him about this:
No ETA, but would hope to see this in a future update at some point!
Hey @danperks , any updates on this?
Hey, we’re working on the code to do this currently, but will end up being a backend fix on our end, so hopefully you just notice it starts working at some point soon!
Similar request here, our MCP is conducting like a deep research kind of call which takes a couple minutes to execute, Cursor’s short timeout is preventing us from completing the request.
Hi,
Any update on that? I have a tool that executes in 3-5 minutes, but from time to time it takes also 30 minutes.
