# NousResearch/hermes-agent · Elevate MCP discovery failures from DEBUG to WARNING

## Open now

- 2 issues, 4 PRs open on GitHub.
- #31246: MCP server misconfiguration is invisible — missing SDK / connection failures logged at DEBUG, never reach gateway.log
- #47509: Gateway: MCP discovery failures logged at DEBUG, invisible at default log level
- PR #31249: fix(gateway): promote MCP SDK missing log from debug to warning with install hint
- PR #46922: fix(tools): upgrade MCP SDK missing messages from debug to warning level
- PR #47520: fix(gateway): log MCP discovery failures at WARNING, not DEBUG
- PR #47623: fix(gateway): log MCP discovery failures at WARNING instead of DEBUG

Multiple issues and fixes address MCP discovery failures and missing SDK errors being logged at DEBUG level, making them invisible at default log settings. The proposed change promotes these log messages to WARNING level, optionally with install hints.

## TL;DR

- 8 member(s): 2 open issue(s), 0 closed issue(s), 4 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.23`: the share of member 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.

## Open related issues

- #31246: MCP server misconfiguration is invisible — missing SDK / connection failures logged at DEBUG, never reach gateway.log
- #47509: Gateway: MCP discovery failures logged at DEBUG, invisible at default log level

## Prior & competing PRs

- **#31249: fix(gateway): promote MCP SDK missing log from debug to warning with install hint**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `tests/tools/test_mcp_tool.py`, `tools/mcp_tool.py`
- **#46922: fix(tools): upgrade MCP SDK missing messages from debug to warning level**. open
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#31249`, `#31246`, `#22168`
  - files: `tests/tools/test_mcp_tool_missing_warning.py`, `tools/mcp_tool.py`
- **#47520: fix(gateway): log MCP discovery failures at WARNING, not DEBUG**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `gateway/run.py`, `tests/gateway/test_runner_startup_failures.py`
- **#47602: fix(gateway): log MCP discovery failures at WARNING (#47509)**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#47520`, `#47509`, `#47520`, `#47520`
- **#47623: fix(gateway): log MCP discovery failures at WARNING instead of DEBUG**. open
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#47520`, `#47509`, `#47520`, `#47520`
  - files: `gateway/run.py`
- **#49438: fix(gateway): elevate MCP discovery failure from DEBUG to WARNING**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`