MCP server request timeout.
When I use AI-interaction tool, there is always a request timeout error after 2 minutes, my AI-interaction tool response always takes longer than 2 minutes, previous versions of Cursor did not have this error.
Steps to Reproduce
Use MCP Server.
When I use AI-interaction tool, there is always a request timeout error after 2 minutes, my AI-interaction tool response always takes longer than 2 minutes, previous versions of Cursor did not have this error.
Expected Behavior
Timeout.
When I use AI-interaction tool, there is always a request timeout error after 2 minutes, my AI-interaction tool response always takes longer than 2 minutes, previous versions of Cursor did not have this error.
When I use AI-interaction tool, there is always a request timeout error after 2 minutes, my AI-interaction tool response always takes longer than 2 minutes, previous versions of Cursor did not have this error.
In old versions, MCP Server usually timeout around 10 minutes. Why in this version it is only 2 minutes, many of my MCP Servers cannot work because of continuous timeout.
Hi @DemonVN at this time the timeout is reduced to avoid issues with AI API request caching on certain providers. I will pass your feedback to our team.
Hey, this looks to not be an error on us, but actually an error with your MCP server itself timing out - the error you see in the screenshot is actually the data coming back from your MCP server.
I’d recommend checking your MCP server to confirm what may be going wrong here!
My AI-interaction tool generates a UI with input to type a message. I only have about 60 seconds to take a photo, read web docs, collect information, attach files/folders, and type a message. How is that enough? At least give me 5 minutes? Is it a violation if the MCP Server takes a long time to respond?
No, I SURE to you that: before upgrading to version 1.5.1, my MCP server could wait up to 10 minutes without timeout. @danperks
I tried redownloading version 1.4.2 and it still held up for 10 minutes, enough for me to do a lot of AI-interaction work, while version 1.5.1 the tool timed out the request for about 60 seconds.
I am not sure how your last screenshot uses elicitation but that MCP feature asks user for input very similar to your previous screenshot. See the linked docs.
Ok Elicitation is good. So I have 60 seconds to interact with Elicitation? The problem is that the timeout is too fast. I’m just wondering why you guys set the timeout so short. I have other ways to deal with the fast timeout, but I’m annoyed by this, what’s wrong with MCP Server taking so long to respond?
