Cairn
NousResearch/hermes-agent

Fix MCP HTTP server crash from JSON string headers

Cluster 53915 · mcp. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These issues and pull requests address a bug where MCP HTTP servers crash on startup when headers in config.yaml are configured as a JSON string rather than a parsed object. The fixes add handling to parse or tolerate that format without crashing.

Open issues1

  • Issue#53915fix(mcp): HTTP servers crash on startup when headers configured as JSON string in config.yaml

Open PRs1

  • PR#53916fix(mcp): handle JSON-string headers in config.yaml

1 PR closed without merging

From the close comments: duplicate 1

  • #53984 fix(mcp): handle JSON string headers config without crashing · duplicate → #53916
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
mcp
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/53915.json
cluster/53915.md