When I opened agentview, all MCP plugins were forcibly enabled. Turning them all off stopped the crashes. It seems there might be an issue where only the plugins I use are enabled in editorview, but switching to agentview enables all of them.
Hey, thanks for the report, and for finding a workaround right away. You’re correct. This is a known pattern: when you open the Agent Window Glass, it initializes all enabled MCP servers at the same time. If you have a lot of them, or if one of them is heavy, the renderer can run out of memory and crash with code 5. We’re tracking the issue, but there’s no ETA for a fix yet.
A couple things that would help us dig deeper:
How many MCP servers do you have in your config ~/.cursor/mcp.json or via the UI? Also, do you have one or two that are especially heavy, like something with a large schema dump or a slow startup? If you enable them one by one, you can usually find the one causing it.
If you can find a crash log in ~/Library/Logs/Cursor/ or in Console.app > Crash Reports > Cursor, please share it here. It will help our team look at the specific stack.
About only needed servers being enabled in the editor view, but all servers being enabled in the agent view. Can you clarify where you saw that? Was it in the plugin list in the + menu in Agent Window, or somewhere else? Agent Window shows the full list of configured servers, but the enabled or disabled state should be shared across both modes. A screenshot of both lists, if possible, would really help confirm whether this is a real mismatch or just a UI confusion.
For now, as a workaround, keep enabled only the MCP servers you actually need.
To prioritize development, we resolved the crash 05 issue by causing a crash during a Cursor reinstallation. While this type of real-world log is extremely rare, it’s incredibly time-consuming for the user (me), so I absolutely won’t send it. It’s not wise to dedicate precious work time to such a task. Therefore, I suggest that if a user provides a log that helps resolve a known issue with Cursor, and that log proves useful, we should grant that user an API token. A similar example is the game Escape from Tarkov, where players who report cheaters or provide console logs of bugs are given in-game items. I believe there was a report that this actually increased the number of reports.
Thanks for the feedback on the idea of rewards for reports.
And no worries about the logs, we don’t want you spending a lot of time on that. Your report is already enough. We know the mechanism renderer OOM when initializing many MCP servers at the same time when opening the Agent Window, and the issue is being tracked. There’s no ETA for a fix yet.
The workaround you found is correct. Keep enabled only the MCP servers you actually use. If the crash happens again with a minimal set of plugins, or if you notice that the enabled or disabled state is actually different between the Agent Window and the Editor View, please let us know. That would be helpful.
Hey @Leonardo_Ollero_Lope, there’s no ETA for the fix yet. The fact that the crash still happens with all MCPs turned off is an interesting signal, it’s not exactly the same scenario as the thread author had. To figure out if we should dig in the same direction or if this is a separate bug, I need a bit more detail:
What Cursor version and OS are you on?
Does the crash still happen if you temporarily rename or clear ~/.cursor/mcp.json and restart Cursor, meaning there’s no MCP config at all, not just disabled in the UI?
If you’re on macOS, can you check Console.app > Crash Reports, search for Cursor, and share the latest crash log? Or the file from ~/Library/Logs/Cursor/. No need to spend a lot of time, just one stack trace is enough.
With that info I can tell whether it’s the same pattern or not.
The stack trace you shared V8/Electron, renderer main thread matches the same renderer crash pattern we’re already tracking in this thread, so at first glance this looks like the same family of issues. The interesting part is that you can reproduce it after clearing ~/.cursor/mcp.json, and you mention that some MCPs come from extensions or plugins and don’t get removed when you clear the file. That lines up with a known gap: MCP servers registered via the extension API live outside mcp.json and can’t always be disabled from the MCP UI, so they still get initialized when you open the Agent Window.
Two things that would help confirm this:
Try launching with extensions disabled: fully quit Cursor, then run cursor --disable-extensions in your terminal and open the Agent Window. If the crash goes away in this mode, we’ve narrowed it down to an MCP registered by a plugin.
If it does go away, can you list which extensions you have installed and which ones register MCP servers, anything that adds tools or integrations? Usually enabling extensions one by one helps find the heaviest one.
We’re tracking the issue, but there’s no ETA for a fix yet. Let me know how it goes with --disable-extensions.
