Stale Customize / Tools workspace scopes cannot be removed and keep spawning extension-host processes

[Oleg_B]

This looks related to these confirmed Cursor MCP lifecycle/cache bugs:

MCP server processes are not terminated and accumulate over time, causing memory leaks

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug Cursor IDE continuously spawns new MCP server processes but does not properly terminate old ones. As a result, the number of running MCP processes grows indefinitely, consuming system memory and eventually degrading system performance. Steps to Reproduce 1. Open Cursor IDE. 2. Work with any project that triggers MCP server usage 3. Observe system processes while interacting with MCP-backed features (e.g., via ps aux, Act…

MCP plugin process not terminated on disable, uninstall, or restart — causes browser tab spam (macOS)

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug Related to the closed thread: MCP server process is not terminated That bug was acknowledged in Nov 2025 but appears unresolved. My case adds three new data points: Plugin uninstall does not kill the process The original report covers the toggle. In my case, fully uninstalling the plugin via the Plugins panel also leaves the process running. Cursor restart relaunches the process The orphaned process is not just le…

In my case, the stale entries are workspace scopes in Customize / Tools & MCPs, not active MCP server configs. They reappear after restart and spawn Cursor Helper extension-host processes. It looks like stale internal workspace/tool state is being rehydrated from Cursor’s internal cache.

Can Cursor provide the supported cleanup path for stale Customize workspace scopes? Is deleting globalStorage/state.vscdb still the recommended workaround for this case?