-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Made a PR for fixing this |
Beta Was this translation helpful? Give feedback.
-
|
Remote stdio command issues on VS Code Remote are common — here's how to fix: The problem: Solutions: 1. Install MCP server on remote # On remote machine
npm install -g @modelcontextprotocol/server-filesystem2. Use absolute paths in config {
"mcpServers": {
"filesystem": {
"command": "/home/user/.nvm/versions/node/v20.0.0/bin/node",
"args": ["/home/user/.nvm/versions/node/v20.0.0/lib/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js"]
}
}
}3. Check PATH on remote # SSH to remote, verify
which node
which npx4. Use remote's shell profile {
"command": "/bin/bash",
"args": ["-c", "source ~/.bashrc && npx @mcp/server"]
}5. Debug with verbose logging # On remote
DEBUG=* npx @mcp/server 2>&1 | tee /tmp/mcp.logCommon issues:
We deploy coding tools remotely at RevolutionAI. The absolute paths approach is most reliable. What's your remote setup — SSH, Docker, or WSL? |
Beta Was this translation helpful? Give feedback.
-
|
Hello, The main issue is caused by the fact that recent changes in the Anyway, thanks again for you time! |
Beta Was this translation helpful? Give feedback.

Made a PR for fixing this
#10464