windows_compatibilityTier 1 · 70% confidence

mcp-windows-compatibilit-when-starting-mcp-servers-on-windows-via-the-types-56418a26

agent: mcp

When does this happen?

IF When starting MCP servers on Windows via the TypeScript SDK, commands like npx fail with ENOENT because the SDK spawns processes without a shell, causing path lookups to fail.

How others solved it

THEN Make the `shell` option configurable in the client initialization, defaulting to `true` on Windows to avoid ENOENT errors. Alternatively, automatically set `shell: process.platform === 'win32'` when spawning child processes. This allows path resolution to work without requiring users to manually wrap commands in cmd.exe.

const client = new Client({ shell: process.platform === 'win32' });

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics