MCP servers: npx not recognized when installed with nvm

[mahdi-malv]

Describe the bug

When tying to add an mcp that uses nvx, and the nvx is accessible through .nvm, the path will not be recognozed

# where npx
~/.nvm/versions/node/v22.14.0/bin/npx

Versions

• Copilot for Xcode: 0.34.117
• Xcode: 16.0
• macOS: 15.4.1

Steps to reproduce

1. Have your npx command accessible through node version manager

2. Import an nvx server such as brave-search

   {
       "servers": {
           "brave-search": {
             "command": "npx",
             "args": ["-y", "@modelcontextprotocol/server-brave-search"],
             "env": {
               "BRAVE_API_KEY": "API_KEY"
             }
           }
       }
   }

3. Save and reload

Screenshots

Logs

...

[2025-05-13T11:43:47.158Z] [info] [GitHubCopilot] [70572] window/logMessage: {
  "message" : "[CopilotMCP] Error initializing MCP server brave-search: Error: spawn npx ENOENT\n    at Process.ChildProcess._handle.onexit (node:internal\/child_process:285:19)\n    at onErrorNT (node:internal\/child_process:483:16)\n    at processTicksAndRejections (node:internal\/process\/task_queues:82:21) {\n  errno: -2,\n  code: 'ENOENT',\n  syscall: 'spawn npx',\n  path: 'npx',\n  spawnargs: [ '-y', '@modelcontextprotocol\/server-brave-search' ]\n}",
  "type" : 1
}

...

Additional context

• Issue doesn't occur for uvx servers such as fetch

# where uvx
/opt/homebrew/bin/uvx

[testforstephen]

@mahdi-malv thanks for reaching out. We're fixing the bin path detection logic. Currently you can configure npx absolute path in mcp.json to temporarily workaround it.

[mahdi-malv]

@testforstephen Thanks.
But more importantly, I confirm, the issue is fixed in 0.34.118

Keep it up guys 💪
I'm closing the issue

[testforstephen]

glad it helps. thank you for confirmation.