Windows managed Node launcher resolution for MCP
Cluster 111937. Data as of
Nothing open on GitHub. Fix merged in #112242 on 16 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 #112242. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #112242. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address MCP stdio servers failing on Windows when using managed Node, due to missing 'bin\' path segment and absent '.cmd' extension in launcher candidates. The work targets correct resolution of npx.cmd and npm.cmd in that environment.
Open issues0
Open PRs0
Fixes on record
-
#112242 fix(mcp): Windows managed Node launchers (npx.cmd/npm.cmd) resolve for stdio MCP servers (#111937, salvage #111941)
files:
tests/tools/test_mcp_tool_issue_948.py,tools/mcp_tool_config.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#111941 fix(mcp): resolve managed Windows Node launchers · merged via another change →
8e11666,#112242
Closed issues · 1
- Closed#111937[Windows] MCP `command: npx` still fails after #37665 — managed Node is at <HERMES_HOME>\node (no `bin\`), and fallback candidates omit the `.cmd` extension
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
- #112242
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026