Hey, thanks for the report. This is a confirmed regression in Cursor 2.0.34 affecting MCP client initialization.
We found a related report with the same root cause: MCP Server Race Condition Causes Infinite Process Spawning on Windows (Cursor 2.0.34)
The MCP extension spawns duplicate client instances before the first connection completes, causing:
- Docker container name conflicts (your case)
- Infinite Node.js process spawning on Windows (other report)
Your workaround using unique container names is solid and should help until a fix is released. I’m escalating both reports to the engineering team since this is a critical infrastructure issue.
I’ll update the thread as soon as there’s progress. Thanks for the logs and clear reproduction steps!