MCP startup summary missing failing server details
Cluster 114746. Data as of
Nothing open on GitHub. Fix merged in #116997 on 20 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 #116997. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116997. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the MCP startup summary reported only counts of failing servers without naming them or their error reasons. Multiple fix attempts address logging the specific server names and connect errors in the summary.
Open issues0
Open PRs0
Fixes on record
-
#116997 fix(mcp): startup summary names every failed server with its connect error (#114746, slim redo of #114794 #114872)
files:
tests/tools/test_mcp_startup_summary_names_failures.py,tools/mcp_tool_discovery.py,website/docs/user-guide/features/mcp.md
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#114746[Bug]: MCP startup summary reports only counts — failing server names and reasons are never logged
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
- Merged PRs
- #116997
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026