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.

These 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

No open issues.

Open PRs2

  • PR#21669fix(cli): discover MCP tools on direct startup
  • PR#23258fix(cli): discover mcp tools on direct startup
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.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
0 PRs closed without merging

For your agent

The same facts, typed.