Project-level MCP server config file support
NousResearch/hermes-agent · cluster 23130 · mcp
Data as of
2 open items. Fix attempted, not merged.
The short answer
2open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue 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
- 2 issues and 0 PRs. Broad area: open items may be separate problems.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs concern adding support for loading MCP server configurations from project or workspace-scoped config files, similar to VS Code's .vscode/mcp.json pattern. They explore scoping MCP server definitions to individual projects rather than only global configuration.
Open issues2
Open PRs0
1 PR closed without merging
From the close comments: closed without comment 1
- #51135 feat: load project mcp json servers · closed without comment
Closed issues · 1
- Closed#51069[Feature]: Support utilizing project .mcp.json MCP server configs
How this cluster was grouped
-
Link evidence (
partly structural links): 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.29: 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
- mcp
- Closed issues
- 1
- Attempts
- 1 PR closed without merging