Issues on Windows 11

[essovius]

Hello, I've just tested it on Win11 and here's my notes.

• using directly via npx mcp-shell won't work.
• you should install it npm install -g mcp-shell
• then you should edit claude_desktop_config.json :

"shell-server": {
  "command": "C:\\Program Files\\nodejs\\node.exe",
  "args": ["C:\\Users\\{REPLACE_USERNAME}\\AppData\\Roaming\\npm\\node_modules\\mcp-shell\\build\\index.js"]
 }

• it works with commands like npm --version
  

• but it doesn't work with folder specific commands:
  
  because it adds double backslash while win11 only works with one backslash.

[Superfishintights]

Thanks for that, got it working but it's refusing to do just about anything so far saying that while it has run_command function, it's very limited.

[essovius]

Thanks for that, got it working but it's refusing to do just about anything so far saying that while it has run_command function, it's very limited.

I don't have windsurf installed but it tried to run. But just sees it as Unix-like environment. weird. maybe you should change writing style or instructions.

UPDATE:

[Superfishintights]

Yeah, figured it out around the same time. Nice one!

I think once you get it doing something easier (and using cmd commands instead of PS), it's fine - and lets its guard down more for other commands. So for anyone else - don't start off with asking it to do anything that could trigger its guard rails - things related to claude or stuff like that.

I also commented out the blacklisted commands just to give it more freedom (I'm happy to own the risk - wouldn't recommend if using any prod server or server you're not happy to have broken).

Now to see if I can get it connected to my linux server which was the initial plan for this. Be a bit trickier but I'm sure there's a way.

[matildepark]

Patched the first one in #6. It would be better if it was always one command, sets config for you, etc.

Now -- as for our commands here ... I've been trying to figure out how to get that settled.

I wrote a utility to find our Powershell and use that as a shell but it seems like it's our string escaping that's a little weird, perhaps?

I also think execa isn't piping our environment into the shell environment like it does on Unix machines... They have an ongoing issue about Windows. shell: true, like we have here, uses cmd.exe, and that seems to provide more functionality than running PS, since when I set it to PS nothing works at all, silently.