Cairn
NousResearch/hermes-agent

MCP OAuth consent and token handling from chat platforms

Cluster 78169 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These items all concern connecting OAuth-protected MCP servers from a chat or gateway context. Themes include showing consent URLs in the originating platform, using a device flow via a /mcp command, and associating OAuth tokens with the requesting user.

Open issues1

  • Issue#78169[Feature]: Surface headless MCP OAuth consent URLs in the originating platform

Open PRs2

  • PR#79449feat(mcp): associate OAuth tokens with requesting user and surface consent in chat
  • PR#140206feat(gateway): /mcp — connect an OAuth MCP server from chat with the device flow
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.00 means 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 Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/78169.json
cluster/78169.md