> MCP causes Cursor to run out of memory and crash.

[GICristian]

When connecting Cursor to the WordPress MCP (by Automattic), the editor’s memory usage starts increasing exponentially until it reaches 100% and the window crashes with an oom (out of memory) error.

The crash happens even on clean installations (no extensions, empty workspace). Disabling the MCP integration immediately stops the memory leak, so the issue seems to be tied to how Cursor handles the MCP connection or its responses.

Steps to Reproduce:

Install or enable the WordPress MCP (Automattic).
Connect Cursor to a WordPress site.
Observe memory usage in Task Manager — it continuously rises until Cursor terminates.

Any idea if this is actually a thing or just for me?