Hey, thanks for the report. I can confirm that several of these issues are already tracked and being worked on by the engineering team.
Confirmed and tracked issues:
- Tool calls going to the wrong server
- Temporary workaround: run one MCP server at a time, or rename tools to avoid conflicts - CRITICAL BUG: Cursor routing tool calls to wrong MCP servers
- Multiple simultaneous connections to non-stdio servers
- Race condition causing duplicate containers to be created - MCP Docker containers fail with name conflicts after Oct 29 update
- Auto-reconnection errors
- Multiple parallel reconnection attempts trigger “Error - Show Output” - Auto-reconnection to MCP servers is broken (runs multiple times in parallel, then fails). on/off works OK
- MCP authentication for cursor-agent CLI
- Known limitation in headless/CI environments, there are workarounds but they are manual - MCP servers are not recognized with cursor-cli in a CI environment
We need more information on:
- “Drops all connections if one server fails”
- Could you share logs that show this behavior?
- “50/50 Error show output” when changing mcp.json
- Is this the same as issue #3 above, or a different one?
- If it’s different, please share the MCP logs from
~/Library/Application Support/Cursor/logs/
- “Stops re-trying to connect indefinitely”
- Request IDs or logs would help us understand what’s happening more clearly
Also, please share your exact Cursor version:
- Help > About Cursor > Copy.
The team understands these are high-priority issues, especially the tool routing bug, given the security concerns you mentioned.