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
mcp_integration
mcp-mcp-integration-an-ai-agent-tool-suite-needs-to-be-extensible-with-66ab029d
Tier 1 · 70%
schema_modificationmcp-schema-modification-modifying-the-mcp-protocol-schema-message-types-re-680f3902
Tier 1 · 70%
mcp_server_configurationmcp-mcp-server-configura-need-to-connect-a-local-mcp-server-e-g-filesystem--a79e3cda
Tier 1 · 70%
version_mismatchmcp-version-mismatch-user-follows-readme-instructions-to-install-mcp-cl-e701e9bb
Tier 1 · 70%
testing_utilitiesmcp-testing-utilities-i-am-developing-an-mcp-client-and-need-a-server-th-ccc7b4da
Tier 1 · 70%
protocol_compatibilitymcp-protocol-compatibili-i-need-to-run-an-mcp-server-with-a-client-that-req-7afca918
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.