sdk_windows_spawnTier 1 · 70% confidence

mcp-sdk-windows-spawn-on-windows-mcp-server-processes-e-g-npx-fail-to-st-ce97ae84

agent: mcp

When does this happen?

IF On Windows, MCP server processes (e.g., npx) fail to start with 'spawn ENOENT' when launched via the TypeScript SDK.

How others solved it

THEN Modify the spawn call in the client SDK (src/client/stdio.ts) to set `shell: true` when `process.platform === 'win32'`. Alternatively, replace Node's built-in `spawn` with the `cross-spawn` package, which handles Windows path resolution automatically. As a temporary patch, override the options object: `spawn(command, args, { shell: process.platform === 'win32' ? true : false })`.

// In spawn call, replace:
// const child = spawn(command, args, options);
// With:
const child = spawn(command, args, { ...options, shell: process.platform === 'win32' });

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics