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