NousResearch/hermes-agent
MCP tool discovery on direct CLI startup
Cluster 21663 · hermes cli. Data as of
2 open items. Fix attempted, not merged.
The short answer
0open issues
2open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items address a bug where MCP tools are not discovered when the CLI is invoked directly, and introduce a native MCP client with HTTP transport and reconnection support. The work centers on ensuring MCP server connections and tool discovery work correctly at startup.
Open issues0
Open PRs2
Closed issues · 1
- Closed#21663cli.py invoked directly bypasses discover_mcp_tools(); banner shows "(stdio) — failed" for unconnected servers
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.00means 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 LabAt a glance
- Subsystem
- hermes cli
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging