MCP catalog env vars routed incorrectly to .env
Cluster 116901. Data as of
Nothing open on GitHub. Fix merged in #117647 on 21 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #117647. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117647. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where MCP catalog installation places non-secret environment variables into .env instead of config.yaml. Multiple fix attempts address routing non-secret values to the correct destination.
Open issues0
Open PRs0
Fixes on record
-
#117647 fix(mcp): catalog install keeps .env secrets-only; non-secret env values go to config.yaml (#116901, salvage #117151)
files:
hermes_cli/mcp_catalog.py,hermes_cli/web_routers/mcp.py,optional-mcps/asana/manifest.yaml,tests/hermes_cli/test_mcp_catalog.py,tests/hermes_cli/test_mcp_catalog_env_boundary.py,tools/connectors/mcp.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#117151 fix(mcp): route non-secret catalog env vars to config.yaml instead of .env (#116901) · merged via another change →
dacae4c,#117647
Closed issues · 1
- Closed#116901[Bug]: MCP catalog prompts secrets and non-secrets into .env
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.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
- Merged PRs
- #117647
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 21 Sep 2026