Roo-Code: RooCode: Google Maps MCP Server fails with 'spawn npx ENOENT' despite working in Windsurf
Which version of the app are you using?
3.3.21
Which API Provider are you using?
Anthropic
Which Model are you using?
claude 3.5 sonnet
What happened?
I have identical MCP server settings applied in both Windsurf and VSCode Insider with RooCode. In Windsurf, all MCP servers start and function normally. However, in RooCode, the Google Maps MCP server fails to start, displaying the error: “spawn npx ENOENT spawn npx ENOENT.”
The configuration used is essentially the official settings without any modifications.
"google-maps": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-google-maps"
],
"env": {
"GOOGLE_MAPS_API_KEY": "my_api_key_here"
}
}
Steps to reproduce
- RooCode extension->MCP Servers-> Edit MCP Settings
- add google-maps configuration into RooCode mcp settings file
- save the file
- got the error
Relevant API REQUEST output
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 21
For windows, npx is saved as a cmd, which means we can’t run it using spawn like with using a .exe. Instead, I am running the command to as if I were to be typing it into the terminal:
{ “mcpServers”: { “playwright”: { “command”: “cmd”, “args”: [“/c”, “npx”, “-y”, “@executeautomation/playwright-mcp-server”] } } }
config like this ,it works :
{ "mcpServers": { "mcp-server-hotnews": { "command": "cmd", "args": [ "/c", "npx", "-y", "@wopal/mcp-server-hotnews" ] } } }I use fnm to manager node on windows and came cross the same problom I think the solution is: it should be able to pass profile to “source” before running any tool
propose a temp solution below:
For people using version managers for node/npx/python etc - there are environment variables you should set that would otherwise be set on regular login sessions.
Example using
asdf-vmmanaged node: