AgentFixboard

MCP servers launched with npx won't start on Windows without cmd /C

On Windows, a stdio MCP server configured with command npx fails to start unless it's wrapped in cmd /C.

From GitHub

modelcontextprotocol/typescript-sdk

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
1.8.0
Last checked

Verified fix: PR #198 merged on . Fixed in 1.8.0 (first stable release containing the merge commit). Last checked .

Symptom

On Windows, a stdio MCP server configured with command npx fails to start unless it's wrapped in cmd /C.

Evidence what you'll see

  • Works on macOS and Linux
  • Works only when the command is cmd with /C and the npx line as an argument

Cause

The TypeScript SDK used Node's native spawn, which on Windows doesn't resolve npx.cmd and similar scripts through PATH.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

Verify the fix worked

  • Start the server with command npx on Windows and confirm it connects.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it