Cairn
NousResearch/hermes-agent

MCP server names misidentified as unknown toolsets

Cluster 109791 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
0 issues and 1 PR.

These issues and PRs address a bug where MCP server names listed in platform_toolsets are incorrectly flagged as unknown toolsets by the CLI. The fix prevents valid MCP server entries from being treated as unrecognized platform toolset identifiers.

Open issues0

No open issues.

Open PRs1

  • PR#109802fix(cli): stop flagging enabled MCP server names as unknown platform toolsets

1 PR closed without merging

From the close comments: duplicate 1

  • #109875 fix(cli): MCP server names in platform_toolsets are not unknown toolsets · duplicate → #106715, #109802
Closed issues · 1
  • Closed#109791platform_toolsets entries that are MCP server names are reported as unknown toolsets
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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/109791.json
cluster/109791.md