spawn npx ENOENT

Common Problems

• MCP TypeScript client custom env removes PATH and causes spawn npx ENOENT

  ## Problem - MCP TypeScript client custom env removes PATH and causes spawn npx ENOENT ## Observed symptom - The stdio connection works without env overrides and fails with spawn npx ENOENT when a custom env is supplied. - Observed in 1 reviewed public artifact; this is not a claim that only that many reports exist. ##

  Last substantive update: 2026-09-11T00:10:00.000Z

• spawn npx ENOENT in a desktop MCP client while the terminal works

  ## Problem - spawn npx ENOENT in a desktop MCP client while the terminal works ## Observed symptom - A desktop editor/client reports spawn npx ENOENT, but npx resolves in an interactive terminal. - Observed in 3 reviewed public artifacts; this is not a claim that only that many reports exist. ## Exact error or signatur

  Last substantive update: 2026-09-11T00:10:00.000Z

• Claude Desktop cannot resolve npx installed through a shell version manager

  ## Problem - Claude Desktop cannot resolve npx installed through a shell version manager ## Observed symptom - npx works in fish/zsh, but Claude Desktop reports spawn npx ENOENT for npm MCP servers. - Observed in 2 reviewed public artifacts; this is not a claim that only that many reports exist. ## Exact error or signa

  Last substantive update: 2026-09-11T00:10:00.000Z

• Bare npx command fails to launch MCP servers on Windows

  ## Problem - Bare npx command fails to launch MCP servers on Windows ## Observed symptom - A Windows MCP host reports spawn npx ENOENT or EINVAL while a shell or explicit Node executable can start the server. - Observed in 4 reviewed public artifacts; this is not a claim that only that many reports exist. ## Exact erro

  Last substantive update: 2026-09-11T00:10:00.000Z

Official primary references

• Node.js child_process documentation

Related hubs

deploy authentication