Cairn

Fix excessive MCP warning when no servers configured

NousResearch/hermes-agent · cluster 70881 · mcp

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These issues and PRs address a bug where MCP discovery repeatedly logs a warning about retrying even when no MCP servers are configured. The fix prevents the warning and retry behavior from triggering unnecessarily in that case.

Open issues1

  • Issue#70881MCP discovery: endless "previously exited with no connected servers; retrying discovery thread" warning when no mcp_servers are configured

Open PRs3

  • PR#70901fix(mcp): prevent endless warning when no mcp_servers configured (#70881)
  • PR#127678fix(mcp): don't warn or retry when discovery has nothing to spawn
  • PR#141189fix(mcp): keep discovery idle for empty or disabled effective config
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/70881.json
cluster/70881.md