[DOCS] MCP docs do not explain deduplication for Claude.ai connectors with the same upstream URL

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/mcp

Section/Topic

"Scope hierarchy and precedence" and "Use MCP servers from Claude.ai"

Current Documentation

The docs currently say:

When the same server is defined in more than one place, Claude Code connects to it once, using the definition from the highest-precedence source: 1. Local scope 2. Project scope 3. User scope 4. Plugin-provided servers 5. claude.ai connectors The three scopes match duplicates by name. Plugins and connectors match by endpoint, so one that points at the same URL or command as a server above is treated as a duplicate.

Later, the Claude.ai connectors section says:

If you've logged into Claude Code with a Claude.ai account, MCP servers you've added in Claude.ai are automatically available in Claude Code: Claude.ai servers appear in the list with indicators showing they come from Claude.ai.

What's Wrong or Missing?

Changelog v2.1.121 added this behavior:

Claude.ai connectors with the same upstream URL are now deduplicated instead of appearing as duplicates

The current MCP docs explain deduplication when a connector duplicates a higher-precedence local/project/user/plugin server, but they do not explain what happens when multiple Claude.ai connectors themselves point at the same upstream URL.

That leaves a gap in the documented deduplication rules for connectors. Users and admins cannot tell whether duplicate Claude.ai connector entries are expected, whether identical upstream URLs collapse into one entry, or how Claude Code decides what appears in the connector/MCP list.

Suggested Improvement

Add a short note in the MCP deduplication rules and/or the Claude.ai connectors section that explicitly states:

• Claude.ai connectors are deduplicated by upstream URL.
• If multiple Claude.ai connectors resolve to the same upstream URL, Claude Code shows one effective connector instead of multiple duplicate entries.
• If there is a deterministic winner/selection rule, document it; if not, document that duplicates are simply collapsed in the UI/tool list.

This would make the v2.1.121 behavior discoverable for users troubleshooting missing or duplicate connector entries.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/mcp | Scope hierarchy, duplicate handling, and Claude.ai connector behavior |

Total scope: 1 page affected

Source: Changelog v2.1.121

Exact changelog entry: Claude.ai connectors with the same upstream URL are now deduplicated instead of appearing as duplicates