Cairn
NousResearch/hermes-agent

hermes dump miscounts configured MCP servers as zero

Cluster 139829 · hermes cli. 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.

One bug report says hermes dump always shows mcp_servers: 0 because it reads mcp.servers while servers are configured under top-level mcp_servers. Two pull requests aim to change the CLI dump to count the configured MCP servers; their status is not stated.

Open issues1

  • Issue#139829[Bug]: `hermes dump` always reports `mcp_servers: 0` (reads `mcp.servers`, servers live at top-level `mcp_servers`)

Open PRs1

  • PR#139833fix(cli): count configured MCP servers in dump

1 PR closed without merging

From the close comments: other 1

  • #143003 fix(cli): count top-level mcp_servers in hermes dump · other → #139833
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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/139829.json
cluster/139829.md