Roo Code 3.9.0+ MCP servers not showing in MCP settings after saving config (Windows/Linux)
After upgrading Roo Code to 3.9.0 or later, MCP servers I add in the MCP settings JSON disappear from the MCP pane, even though they showed up on 3.8.6. Users on Windows and Linux report the same thing when using npx or node-based servers. Is there a way to get the servers to appear?
Originally asked on GitHub: https://github.com/RooCodeInc/Roo-Code/issues/2085
8 answers
The thread does not contain an official fix. The issue was closed as NOT_PLANNED, and the reported symptom is that servers launched via npx or node silently fail to spawn from 3.9.0 onward, so the configuration card never appears. Commenters found workarounds that made the card show.
On Windows, wrap the command in cmd with the /c flag:
json{ "mcpServers": { "sequential-thinking": { "command": "cmd", "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-sequential-thinking"] } } }On Linux, one user reported that replacing
npxornodewith the absolute path to the binary (for example from an nvm installation) made the servers show up. Another found that the spawned process could still fail with/usr/bin/env: 'node': No such file or directory, so PATH may matter. A wrapper shell script that loads nvm and then runs npx also worked for one user. Restarting VS Code sometimes restored the card.Also note that Roo may save MCP config to a different file (
mcp_settings.jsonversuscline_mcp_settings.json) than the one opened by Edit MCP Settings. If the card is missing, check which file was updated. General advice: downgrading to 3.8.6 lets you see the spawn error card while you debug the config.Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Reporter upgraded from 3.8.6 to 3.9.0 and later versions with a Brave or mcp-Atlassian config; the MCP pane went blank on 3.9.0+ while 3.8.6 showed the servers. Reported 3.10.5 also failing.
Source: https://github.com/RooCodeInc/Roo-Code/issues/2085 (opens external site)
Did this work for you?What @TheMackey tried on GitHub (Worked)
Windows user changed the command to cmd with args starting with /c followed by npx and the package name, which made the server card appear after saving.
Source: https://github.com/RooCodeInc/Roo-Code/issues/2085#issuecomment-2764372002 (opens external site)
Did this work for you?What @truecalifornian tried on GitHub (Partly worked)
User found Roo saved to cline_mcp_settings.json while Edit MCP Settings opened mcp_settings.json; after Roo was told to save to mcp_settings.json, servers showed but kept timing out and needed manual restarts.
Source: https://github.com/RooCodeInc/Roo-Code/issues/2085#issuecomment-2764680184 (opens external site)
Did this work for you?What @binduwavell tried on GitHub (Partly worked)
Linux user used absolute paths for node/npx and for any script args, which worked in 3.10 but the list went blank again in 3.11.3.
Source: https://github.com/RooCodeInc/Roo-Code/issues/2085#issuecomment-2774218343 (opens external site)
Did this work for you?What @binduwavell tried on GitHub (Partly worked)
Restarting VS Code made the servers show again on 3.11.3; the user suspected a node version incompatibility for an intermittent server.
Source: https://github.com/RooCodeInc/Roo-Code/issues/2085#issuecomment-2774235778 (opens external site)
Did this work for you?What @diramazioni tried on GitHub (Didn't work)
Linux user set the command to the full nvm node path for npx; the server appeared but failed with /usr/bin/env: 'node': No such file or directory.
Source: https://github.com/RooCodeInc/Roo-Code/issues/2085#issuecomment-2780629385 (opens external site)
Did this work for you?What @diramazioni tried on GitHub (Worked)
Wrapper bash script sets HOME, loads nvm.sh, then execs npx with the postgres server package; command set to the script path in mcp.json.
Source: https://github.com/RooCodeInc/Roo-Code/issues/2085#issuecomment-2781315129 (opens external site)
Did this work for you?