RFC 8628 device-code OAuth flow for MCP servers
Cluster 104742. Data as of
Nothing open on GitHub. Fix merged in #104891 on 7 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 #104891. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104891. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members all concern adding RFC 8628 device authorization grant (device-code flow) support to MCP OAuth login. The work covers the feature request, implementation, and a related authorization change.
Open issues0
Open PRs0
Fixes on record
-
#104891 feat: authorize MCP servers with device codes (#104742)
files:
evals/mcp_device_flow.py,hermes_cli/mcp_config.py,hermes_cli/subcommands/mcp.py,tests/tools/test_mcp_device_flow.py,tests/tools/test_mcp_oauth.py,tools/mcp_oauth.py,tools/mcp_oauth_device.py,tools/mcp_oauth_provider.py,website/docs/reference/mcp-config-reference.md
1 PR closed without merging
From the close comments: partial fix 1
-
#104752 feat: RFC 8628 device-code flow for MCP OAuth login · partial fix →
f5afe8b,965f18b,f94307a,#104742,#104891
Closed issues · 1
- Closed#104742[Feature] Add RFC 8628 device-code flow support for MCP OAuth
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
- #104891
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Sep 2026