Cairn
NousResearch/hermes-agent

MCP OAuth not triggering for servers without authentication challenge

Cluster 89412 · mcp. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These members concern MCP OAuth handling when a server does not challenge unauthenticated requests, such as Google's Gmail MCP, including forcing the OAuth flow after a 200 response to initialize. One member also mentions honouring a configured oauth.scope and accepting Google's root-slash issuer, which are adjacent OAuth details.

Open issues1

  • Issue#89412MCP OAuth flow never triggers for servers that don't challenge unauthenticated requests (e.g. Google's Gmail MCP)

Open PRs1

  • PR#144307fix(mcp): honour configured oauth.scope, accept Google's root-slash issuer, let login authorize anonymous servers

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #53873 fix(mcp): force OAuth flow when server returns 200 for initialize without auth (#53870) · superseded by another PR → #97010, #53870
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
mcp
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/89412.json
cluster/89412.md