Cairn
NousResearch/hermes-agent

MCP OAuth refresh token persistence fixes

Cluster 109932 · 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 address a bug where MCP OAuth refresh tokens are lost or not carried forward correctly, with fixes targeting storage enforcement and tool-level token preservation. The issues and patches focus specifically on ensuring recovered refresh tokens survive across the full auth flow.

Open issues1

  • Issue#109932[Bug]: Zoho MCP refresh token disappears again after recovery — follow-up to #62333

Open PRs1

  • PR#110201fix(mcp-oauth): enforce refresh_token carry-forward in storage, not just the provider

1 PR closed without merging

From the close comments: other 1

  • #110178 fix(tools): preserve recovered MCP refresh tokens · other → #109932, #111186
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/109932.json
cluster/109932.md