Nothing open on GitHub. Fix merged in #125644 on 28 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 #125644. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #125644. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern how managed Node.js installations interact with MCP stdio servers, specifically around PATH precedence and native addon compatibility when a different Node version built the addon.
Open issues0
Open PRs0
Fixes on record
-
#125644 MCP servers with a native addon built by another Node now say so and name the rebuild under Hermes's Node (#124264)
files:
hermes_cli/mcp_config.py,tests/e2e/core/upgrade/hosts/test_path_shapes.py,tests/tools/test_mcp_node_abi.py,tools/mcp_tool_config.py,tools/mcp_tool_errors.py,tools/mcp_tool_node_abi.py,tools/mcp_tool_transport.py
1 PR closed without merging
From the close comments: other 1
-
#124304 fix(mcp): keep the user's Node ahead of PM's for stdio MCP servers · other →
#124264,#125644
Closed issues · 1
- Closed#124264hermes update installs a managed Node and prepends it to MCP child PATH, breaking npm MCP servers with native addons
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
- #125644
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 28 Sep 2026