Solve conflicts when connecting with multiple MCP servers

[swissspidy]

Tool names quickly clash when you connect to multiple WordPress MCP servers

Prefixing them with the site name might help. Otherwise we would need to find a smart way to only provide the tools from the most suitable server. For example, if I say "Create a new post on my personal blog" vs "Fetch my company's latest posts", we can analyze the prompt to figure out that these are for different MCP servers, and connect to the right one. Of course this gets tricky when you want to do something like "Copy this post from my personal blog to my company site"

[swissspidy]

The Anthropic API doesn't like multiple tools with the same name and errors when that happens.

[swissspidy]

Both Anthropic and Google limit tool names to 64 characters, so prefixing every tool with a potentially long server name is tricky.

[swissspidy]

From Gemini CLI:

If multiple MCP servers expose a tool with the same name, the tool names will be prefixed with the server alias you defined in the configuration (e.g., serverAlias__actualToolName) to avoid conflicts. Note that the system might strip certain schema properties from MCP tool definitions for compatibility.