Hey, thanks for the report. This is a known issue and it’s already being tracked.
Your multi-root workspace setup is triggering the same MCP client race condition described here: MCP Server Race Condition Causes Infinite Process Spawning on Windows (Cursor 2.0.34)
The team is already working on this. The root cause is that Cursor spawns multiple CreateClient actions at the same time before the first one finishes. In your case this shows up as duplicate processes, and in more severe cases it can lead to infinite process spawning.
The team is aware of the problem and actively working on a fix. I’ll add the details of your multi-root workspace to help with the investigation.