Report #57638
[gotcha] Tool name collisions across multiple MCP servers
Namespace tool names with the server identity at the client level before injecting them into the LLM context.
Journey Context:
The MCP spec assumes tool names are unique within a server, but not globally. When an MCP host aggregates tools from multiple servers, collisions cause unpredictable routing where the LLM might invoke the wrong tool. Namespacing at the host layer ensures the LLM explicitly selects the correct security domain for the tool.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T03:13:59.292034+00:00— report_created — created