Basically, now if Cursor’s connection to MCP server closes or disconnects (eg. due to server relaunch or new version deployment), user has to manually toggle off and on in the MCP config window or open a new Cursor window to reconnect. This becomes an issue to our production MCP server since it resets all connections at every deployment and users typically are not aware that the MCP connection is closed in this case.
Is there any mechanism for retry connections automatically?
I redeploy 1-3 times per day in production and 10-20 times per day doing local development. It’s annoying to have to click that toggle twice every time. The Tools & MCP tab is basically always open for me. For my users, it means their connection will randomly fail during a prod redeployment every single day. I cannot assume they are as savvy about this behavior as I am, so it makes me look bad.
+1000 to this. I could wrap an MCP server in a local stdio adapter, but this feels like something that should (at least) be a checkbox in the configuration for Cursor.