Better resilience for MCP services

Feature request for product/service

Cursor IDE

Describe the request

MCP connectivity seems to be very fragile in the current Cursor IDE. If there’s even a brief break in connectivity, one must go into Settings → Tools & MCP Servers and bounce installed MCP servers to get them to reconnect.

It’d be hugely useful if Cursor could attempt to proactively reconnect to disconnected MCP servers when requests are made, and also make an attempt to maintain continuity of MCP server connections in the background so that they’re ready whenever they’re required (leveraging techniques such as adaptive backoff to avoid overwhelming the servers).

Hey, thanks for the feedback. This is a known issue, other users have also requested auto-reconnect: MCP auto-reconnect after server disconnection?

The team is aware of this issue, especially for production deployments.

For now, the workaround is to manually toggle it off and on in Settings → Tools & MCP Servers, or reload the Cursor window.

1 Like

Thanks, @deanrie . Given the number of others who’ve asked for this, it’d be most helpful if this could be prioritized (perhaps the developer whose full-time job is rearranging UI elements in every release or so could be tasked with more useful work…)

1 Like

also would be good at least some better way to visualise that MCP is diconnected outside of settings page.

1 Like