MCP server name collision with built-in toolsets
Cluster 30563 · mcp. Data as of
Nothing open on GitHub. Fix merged in #103943 on 6 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue 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
- Nothing open on GitHub.
These issues and PRs concern a naming conflict where an MCP server name can match a native/static toolset name, causing silent or unexpected behavior. The work involves detecting collisions, warning users, and potentially merging tools rather than silently dropping them.
Open issues0
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
2 PRs closed without merging
From the close comments: merged via another change 1 · stale or abandoned 1
Closed issues · 1
- Closed#30563MCP server name can silently collide with a native toolset; native wins with no warning
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.50: 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
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 6 Sep 2026