MCP server name collision hides tools from search
Cluster 86012 · mcp. Data as of
1 open item. Fix merged in #103943 on 6 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #103943. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read #103943, then check whether your report is the one still open.
Read #103943Pick up a Lab taskIssues and fixes around MCP servers whose names collide with built-in toolsets becoming invisible to tool search. The work addresses how colliding server names are handled so their tools remain discoverable.
Open issues1
- Issue#86012MCP tools registered but absent from tool_search catalog (server-memory)
Open PRs0
Fixes on record
-
#103943 MCP servers named like a built-in toolset no longer vanish from the model (salvage #19793)
files:
tests/test_toolsets.py,tests/tools/test_mcp_dynamic_discovery.py,toolsets.py,website/docs/reference/toolsets-reference.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#86031 fix(mcp): keep colliding MCP servers available to tool search · merged via another change →
245e480,#103943,#19793
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- mcp
- Merged PRs
- #103943
- Closed issues
- 0
- Attempts
- 1 PR closed without merging
- Fix link checked
- 6 Sep 2026