docs: add Windows cmd /c npx workaround to server READMEs#3466
Closed
r266-tech wants to merge 1 commit intomodelcontextprotocol:mainfrom
Closed
docs: add Windows cmd /c npx workaround to server READMEs#3466r266-tech wants to merge 1 commit intomodelcontextprotocol:mainfrom
cmd /c npx workaround to server READMEs#3466r266-tech wants to merge 1 commit intomodelcontextprotocol:mainfrom
Conversation
On Windows, npx is installed as npx.cmd — a batch file shim that child_process.spawn() cannot execute directly without shell: true. MCP clients (Claude Desktop, Claude Code) do not pass shell: true, so npx-based configs silently fail on Windows. Add a note after each NPX config block explaining the issue and showing the cmd /c workaround for affected servers: - filesystem - memory - sequentialthinking - everything Fixes #3460
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
All official MCP server READMEs recommend NPX configs like:
{ "command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", ...] }This silently fails on Windows because
npxis installed asnpx.cmd(a batch script shim), andchild_process.spawn()— used by Claude Desktop and Claude Code — cannot execute.cmdfiles withoutshell: true, which MCP clients don't pass.This is a well-known Node.js-on-Windows issue. Since MCP configs are copy-pasted from READMEs, Windows users hit this immediately with no clear error message.
Closes #3460
Solution
Add a Windows-specific callout after each NPX config block showing the
cmd /cwrapper:{ "command": "cmd", "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-filesystem", ...] }Affected servers
src/filesystem— Claude Desktop + VS Code NPX sectionssrc/memory— Claude Desktop + VS Code NPX sectionssrc/sequentialthinking— Claude Desktop + VS Code NPX sectionssrc/everything— Claude Desktop NPX sectionTesting
Verified the diff is purely additive documentation — no code changes, no functional impact on macOS/Linux users.