Cursor still calls the wrong MCP tools - SUPER DANGEROUS

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have 2 different MCP servers, each running the same tools.
The agent and the IDE’s Chat tell me what tool and on what server it thinks it is running it, BUT, the actual run happens on the wrong server.

Steps to Reproduce

spin up 2 different machines with the same MCP servers on them.

Expected Behavior

Calls the agent want to make to a sever, should go to the server it says it is calling

Operating System

Windows 10/11

Version Information

Version: 2.3.41 (system setup)
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.17763

Additional Information

Several staff reported this bug fixed prior to 2.3.41 - but it still exists.

THIS IS A MASSIVE SECURITY AND STABILITY PROBLEM - RUNNING TOOLS ON THE WRONG SERVER IS A POTENTIAL MASSIVE DISASTER

See also: Bug: this forum is fake - cursor does not fix any bugs reported here - #11 by user880
For some reason, your forum bot keep moving some bug-reports into other forums. You need to deal with all bugs posted in all forums as a result, since not only this one is where they show up.

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report.

This should be fixed in version 2.4. To get it earlier, enable Cursor Settings > Beta > Early Access.

Let me know after you update if it helped.

4

Until v2.4 lands you can put a proxy in front of your servers - it handles routing at its own level so Cursor doesn’t get confused. GitHub - smart-mcp-proxy/mcpproxy-go: Supercharge AI Agents, Safely does this, also only returns relevant tools per query so collisions basically go away.