[Candidate / unverified] Solution for problem-launch-version-manager-shim: Record the absolute path to npx from an interactive shell (which npx). Configure

## Support semantics This is a **candidate / unverified** Solution from the KFA Solution Factory Tier-2 gate. It is source-grounded research material, not an Outcome, and does **not** claim independent reproduction or confirmed field success. ## Cause Desktop applications spawn subprocesses with inherited environment; without version-manager activation, PATH lacks shim directories, so npx is not found and spawn emits ENOENT. ## Steps 1. In the interactive shell where npx works, run which npx and note the absolute path and owning version manager. 2. Compare PATH in a non-login environment (for example env -i zsh -c "echo $PATH; which npx") with your interactive shell. 3. Update Claude Desktop MCP config to use the absolute npx or node path, or install Node via a path already on the desktop PATH (system/Homebrew) if policy allows. 4. Restart Claude Desktop fully after PATH or install changes and retry MCP server load. ## Expected result Claude Desktop spawns the MCP server process without ENOENT; MCP connection succeeds using the configured absolute command path. ## Misleading approaches - Reinstalling every MCP package without fixing command resolution. - Assuming shell RC changes always apply to GUI-launched Claude Desktop. ## Limitations - External reports describe workarounds; no maintainer-confirmed universal fix for all version managers. - Behavior may differ by Claude Desktop version and OS; KFA editorial record cites 2024–2025 reports. - Switching Node install method (for example Homebrew) is one reporter outcome, not established as the only fix. ## Unknowns - Current Claude Desktop PATH inheritance on unreviewed versions and operating systems. ## Evidence claims - (external_report) Public MCP servers issue #436 documents Claude Desktop spawn npx ENOENT after nvm.fish-managed Node while npx works in interactive shells. — https://github.com/modelcontextprotocol/servers/issues/436 - (external_success_report) mise discussion #6645 reports Claude Desktop fails with spawn npx ENOENT because the loader does not run shell init; reporter used direct shim path as workaround. — https://github.com/jdx/mise/discussions/6645 - (documented_platform_behavior) Node child_process spawn resolves executables using the process environment PATH; missing entries cause spawn failures when the command is not found. — https://nodejs.org/docs/latest-v22.x/api/child_process.html