Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] MCP docs do not explain deduplication for Claude.ai connectors with the same upstream URL [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54168•Fetched 2026-04-29 06:34:28
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

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:

PageContext
https://code.claude.com/docs/en/mcpScope 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

extent analysis

TL;DR

Update the documentation for "Scope hierarchy and precedence" and "Use MCP servers from Claude.ai" to include deduplication rules for Claude.ai connectors with the same upstream URL.

Guidance

  • Add a note to the MCP deduplication rules section explaining that Claude.ai connectors are deduplicated by upstream URL.
  • Clarify in the Claude.ai connectors section that if multiple 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.
  • Review the changelog entry for v2.1.121 to ensure the documentation update aligns with the intended behavior.

Example

No code snippet is necessary for this documentation update.

Notes

The suggested improvement should be applied to the affected page (https://code.claude.com/docs/en/mcp) to ensure users can understand the deduplication rules for Claude.ai connectors.

Recommendation

Apply workaround: Update the documentation to reflect the deduplication behavior for Claude.ai connectors, as this will improve the understandability of the feature and align with the behavior introduced in v2.1.121.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#GPU compatibility#latency issue#model loading#dependency error#configuration error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] MCP docs do not explain deduplication for Claude.ai connectors with the same upstream URL [1 participants]