When the MCP server restarts, the MCP in the cursor does not work when using the StreamableHttp type

Feature request for product/service

Cursor IDE

Describe the request

When using StreamableHttp MCP, after the MCP Server restarts, cursor requests will show an “Invalid session ID” exception, and new sessions cannot be reconnected. MCP needs to be closed and then reopened to work normally.
Is it possible to obtain a new session upon receiving an “Invalid session ID” exception?

1 Like

Same experience here. What I would love Cursor to be able to do is react to a restart or even just a connection disruption. It isn’t realistic to expect most users to understand how to create a wrapper to handle this. And, by saying that, I acknowledge that I could create my own client-side wrapper that handles this, but it still feels like it should be baked in to Cursor.