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

**URL:** <https://forum.cursor.com/t/mcp-server-processes-are-not-terminated-and-accumulate-over-time-causing-memory-leaks/143181>\
**Category:** Bug Reports\
**Created:** [November 19, 2025, 8:33am UTC](https://forum.cursor.com/t/mcp-server-processes-are-not-terminated-and-accumulate-over-time-causing-memory-leaks/143181 "2025-11-19T08:33:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![f1nder](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/f1nder/32/4904_2.png) [@f1nder](https://forum.cursor.com/u/f1nder)\
**Post date:** [November 19, 2025, 8:33am UTC](https://forum.cursor.com/t/mcp-server-processes-are-not-terminated-and-accumulate-over-time-causing-memory-leaks/143181/1 "2025-11-19T08:33:01Z")

</div>

### 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, Activity Monitor, or System Monitor).
4.	Cursor repeatedly spawns new MCP server child processes.
5.	Old/however no-longer-used MCP processes are not terminated.

```

### Screenshots / Screen Recordings

 ![Screenshot 2025-11-19 at 15.31.34.png](https://us1.discourse-cdn.com/cursor1/original/3X/5/3/5382db61547089f562a4c00c7e97b9a6fb7387bb.jpeg)

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77  
VSCode Version: 1.99.3  
Commit: ba90f2f88e4911312761abab9492c42442117cf0  
Date: 2025-11-13T23:10:43.113Z (5 days ago)  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 25.1.0

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![f1nder](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/f1nder/32/4904_2.png) [@f1nder](https://forum.cursor.com/u/f1nder)\
**Post date:** [November 19, 2025, 8:35am UTC](https://forum.cursor.com/t/mcp-server-processes-are-not-terminated-and-accumulate-over-time-causing-memory-leaks/143181/2 "2025-11-19T08:35:45Z")

</div>

![Screenshot 2025-11-19 at 15.35.31](https://us1.discourse-cdn.com/cursor1/original/3X/d/5/d54a11db13115d30de37907e7986a6d8f4d6d94d.jpeg)

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [November 19, 2025, 10:53am UTC](https://forum.cursor.com/t/mcp-server-processes-are-not-terminated-and-accumulate-over-time-causing-memory-leaks/143181/3 "2025-11-19T10:53:15Z")

</div>

Hey, thanks for the report! This is a confirmed bug affecting MCP server process lifecycle management starting from Cursor 2.0.34. Several users on Windows and macOS have reported similar issues.

The root cause is a race condition where Cursor starts multiple MCP client instances without properly terminating the old ones.

To help prioritize a fix, could you please share:

- Which MCP server(s) you’re using (from ~/.cursor/mcp.json)
- Logs from your MCP server
- Whether this happens on every Cursor restart or only during active use

I’ll mark this as related to the existing ticket.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [December 11, 2025, 10:53am UTC](https://forum.cursor.com/t/mcp-server-processes-are-not-terminated-and-accumulate-over-time-causing-memory-leaks/143181/4 "2025-12-11T10:53:34Z")

</div>

Closed on December 11, 2025, 10:53am UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
