NousResearch/hermes-agent

MCP server removal leaves orphaned OAuth state files

Cluster 81050 · mcp. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 3 PRs 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 0 PRs.

Removing an MCP server did not clean up associated OAuth state files (.meta.json, .client, .json), causing removed or disabled servers to reappear on gateway restart. Fixes target both the API endpoint and the removal logic to purge this state.

Open issues1

  • Issue#81050MCP server removal is incomplete — orphaned .meta.json revives a disabled/removed server at every gateway restart

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: superseded by another PR 2 · other 1

  • #81063 fix(mcp): always purge .meta/.client/.json OAuth state on mcp remove (#81050) · superseded by another PR → #81059
  • #81077 fix(web): dashboard DELETE /api/mcp/servers/{name} now cleans OAuth state (#81050) · superseded by another PR → #81059
  • #128585 fix(mcp): purge orphan OAuth state on mcp remove (#81050) · other
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.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
3 PRs closed without merging

For your agent

The same facts, typed.