MCP server process is not terminated

[Antonytm]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Cursor does not close MCP server process when it is disabled

Steps to Reproduce

1. I want to use MCP server that is NPM based. Let’s say @modelcontextprotocol/server-everything

2. I configure it in mcp.json:

   “Server everything”: {
   “command”: “npx”,
   “args”: [“@modelcontextprotocol/server-everything”]
   }

3. I open MCP Setting > Tools

4. I enable and disable the server a few times

5. Processes are still present, they are not terminated

It is critical for MCP servers that consumes a lot of memory. And it is critical for MCP servers that use some context. Or use some resources like file or port. Another instance of the MCP server fails due to not properly closed previous ones.

Expected Behavior

The MCP server process should be terminated once you disable it in the Cursor configuration

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.75 (user setup)
VSCode Version: 1.99.3
Commit: 9e7a27b76730ca7fe4aecaeafc58bac1e2c82120
Date: 2025-11-12T17:34:21.472Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

N/A

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. This looks like a bug, MCP server processes should be terminated when you disable them via the toggle.

To help us debug this, could you please share:

• MCP server logs: open the Output panel Ctrl+Shift+U → select “MCP Logs” from the dropdown
• Does this happen with all your MCP servers or only some of them?
• Do the orphaned processes eventually get cleaned up when you fully close Cursor, or do they keep running?

Temporary workaround: manually kill the processes via Task Manager when switching MCP servers on or off.

I’ll pass this to the team, since it’s blocking your workflow.