MCP server connection retry and reconciliation fixes
Cluster 112445. Data as of
Nothing open on GitHub. Fix merged in #113112 on 17 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113112. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113112. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address cases where an MCP server that fails its initial connection is not retried, and where MCP reconciliation in the gateway only triggers on config edits rather than on drift.
Open issues0
Open PRs0
Fixes on record
-
#113112 fix(gateway): an MCP server whose first connect failed is retried without a config edit (#112445, salvage #112447)
files:
gateway/run_profile_reconcile.py,tests/gateway/test_gateway_mcp_oauth_unattended.py,tests/tools/test_mcp_reconcile_with_config.py,tools/mcp_tool_discovery.py,website/docs/user-guide/features/mcp.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#112447 fix(gateway): reconcile MCP on drift, not only on a config edit · done elsewhere →
#113112
Closed issues · 1
- Closed#112445An MCP server whose first connect fails is never retried in the gateway
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
- Merged PRs
- #113112
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 17 Sep 2026