Cairn
NousResearch/hermes-agent

Profile isolation and management for MCP servers

Cluster 4280 · hermes cli. Data as of

Nothing open on GitHub. No fix on record.

The short answer

0open issues
0open PRs
2items grouped
Known?
Yes. 2 related items grouped here, 2 issues already closed.
Fix event
No merged or attempted fix PR is on record for this cluster.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern bugs and feature requests around keeping MCP server configurations scoped to individual profiles, plus dashboard-level tooling for managing multiple profiles. Themes include cross-profile leakage, per-profile CLI scoping, and unified profile switching.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Closed issues · 2
  • Closed#4280[Bug]: MCP servers added in one profile are accessible in another profile.
  • Closed#61765Feature: per-profile MCP scoping (--profile on hermes mcp add/remove/configure/list/test)
How this cluster was grouped
  • Link evidence (automated judgement only): no structural link between members; the grouping rests entirely on an automated relevance judgement over their text.
  • Read the members yourself before treating them as one problem.
  • Pairwise link density 0.36: 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
2
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/4280.json
cluster/4280.md