MCP OAuth DCR client_secret handling fixes
Cluster 29680 · mcp. Data as of
Nothing open on GitHub. Fix merged in #87491 on 16 Aug 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 #87491. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #87491. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern MCP OAuth flows where Dynamic Client Registration (DCR) returns a client_secret that must be included in subsequent token exchange requests. Multiple fixes address propagating and using that secret across OAuth paths, with Supabase cited as a concrete case.
Open issues0
Open PRs0
Fixes on record
-
#87491 fix(mcp): handle DCR clients with secrets across all OAuth paths
files:
contributors/emails/[redacted:email],tests/tools/test_mcp_oauth.py,tests/tools/test_mcp_oauth_manager.py,tools/mcp_oauth.py,tools/mcp_oauth_manager.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#29680MCP OAuth fails with Supabase: token exchange requires client_secret
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
- #87491
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 16 Aug 2026