MCP Tool Routing Ignores Server Name When Multiple Servers Expose Same Tool Name

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When multiple MCP servers are configured that expose the same tool name (e.g., run_snowflake_query), Cursor routes all tool calls to a single server regardless of which server-prefixed tool name is used.

Steps to Reproduce

  1. Configure two MCP servers in .cursor/mcp.json:
{
  "mcpServers": {
    "snowflake_nonphi": {
      "command": "uvx",
      "args": ["snowflake-labs-mcp", "--connection-name", "ACCOUNT_A"]
    },
    "snowflake_deid": {
      "command": "uvx",
      "args": ["snowflake-labs-mcp", "--connection-name", "ACCOUNT_B"]
    }
  }
}
  1. Reload Cursor - both servers start (verified via ps aux)
  2. Use the AI to call mcp_snowflake_deid_run_snowflake_query and mcp_snowflake_nonphi_run_snowflake_query

Expected: Each tool routes to its respective server.
Actual: Both tools route to the same server (verified by SELECT current_account() returning same value for both, and MCP logs showing only one server receiving queries)

Note that this example uses the MCP package snowflake-labs-mcp.

Expected Behavior

Each tool routes to its respective server.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44 (Universal)
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Additional Information

MCP Package: snowflake-labs-mcp

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report.

This is a known issue - when multiple MCP servers expose tools with the same base name, Cursor routes calls to the wrong server. The team is aware and working on a fix.

Workaround: Rename the tool on one of the servers to make it unique (e.g., add a suffix like _accountA to the tool name in the server code), or run only one server at a time.

A previous user confirmed this approach works: CRITICAL BUG: Cursor routing tool calls to wrong MCP servers - #4 by Chris_Drake

3

Great, thank you! Hope a fix comes soon. :smiley:

4

Curious! I tested this just yesterday, and it was working fine for me now.

Version: 2.3.21 (system setup)
VSCode Version: 1.105.1
Commit: 68e0a0385b87408d050869ea543e3778ad53f780
Date: 2026-01-02T23:46:13.381Z
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

This is the download link for the working version:
https://api2.cursor.sh/updates/download/golden/win32-x64/cursor/2.3

1 Like
5

It does work! Cursor 2.3 solves it. Thanks for the heads up!

6

I am not entirely sure this really is fixed - I’m getting intermittent problems still - I think the other bugs with the multi-connection-storm SNAFU tricks us into thinking its fixed, by causing Claude to pick at random, and we think it’s working, when it’s just fluked the one we expected…