MCP's are not working

[HologramSteve]

Summary

MCP's are not working at all. It just says it can't connect on whatever MCP I throw at it. I tested the same MCP with other harnesses (grok) and it worked there.

Expected Behavior

It working.

Actual Behavior

"Failed"

Steps to reproduce the issue

1. Add MCP
2. Done

Command Code Version

v0.1.40 (desktop)

Operating System

Windows

Terminal/IDE

No response

Shell

No response

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

No response

[jiatianyuan11]

Quick triage ideas, since "works in grok but not here" on Windows is usually the command the app spawns failing, not the MCP server itself:

1. PATH gap. GUI apps on Windows often inherit a different PATH than your terminal. If your config runs a bare npx / uvx, the app may not resolve it even though it works in PowerShell. Test: replace the command with npx.cmd or the absolute path to the shim (e.g. C:\Program Files\nodejs\npx.cmd) and retry.

2. Read the failure line type. ENOENT = the command itself was not found (PATH issue above). -32000 / -32603 = the server started and then died; that points at the server's own stderr or a crashed dependency.

3. Run the exact command from your config in a plain terminal. If it works there but not in the app, it is almost always (1).

If you can paste the app's MCP log lines or your config block (redact tokens), I can narrow it further.