[DOCS] MCP docs still describe `cmd /c` as a Windows config requirement
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/mcp
Section/Topic
Option 3: Add a local stdio server / native Windows cmd /c warning for MCP configuration
Current Documentation
The docs currently say:
Windows Users: On native Windows (not WSL), local MCP servers that usenpxrequire thecmd /cwrapper to ensure proper execution. ``bash # This creates command="cmd" which Windows can execute claude mcp add --transport stdio my-server -- cmd /c npx -y @some/package`Without thecmd /cwrapper, you'll encounter "Connection closed" errors because Windows cannot directly executenpx`.
Later on the same page, the config/policy examples use plain npx command arrays:
{ "serverCommand": ["npx", "-y", "@modelcontextprotocol/server-filesystem"] },* Example: ["npx", "-y", "server"] will NOT match ["npx", "server"] or ["npx", "-y", "server", "--flag"]
What's Wrong or Missing?
Changelog v2.1.119 says: Windows: removed false-positive Windows requires cmd /c wrapper MCP config warning.
The current MCP page still presents cmd /c as a blanket Windows requirement. That is outdated for at least some MCP configuration flows, and it leaves Windows users unsure how native Windows configs should actually be written.
This is especially confusing because the same page also documents .mcp.json/policy command arrays using bare npx entries. After v2.1.119, the docs should no longer imply that every Windows MCP config needs a cmd /c wrapper.
Suggested Improvement
Update https://code.claude.com/docs/en/mcp to reflect the v2.1.119 behavior change:
- Remove or rewrite the blanket warning that says native Windows MCP configs require
cmd /c. - Clarify which cases, if any, still need a wrapper versus which config forms should use plain command/arg arrays.
- Add one explicit Windows example for persisted MCP configuration (
.mcp.json,claude mcp add-json, orallowedMcpServers.serverCommand) so users know the correct representation.
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/mcp | Native Windows warning still says npx servers require cmd /c, while the same page also documents bare npx command arrays for MCP config and policy matching |
Total scope: 1 page affected
Source: Changelog v2.1.119
Exact changelog entry: Windows: removed false-positive Windows requires cmd /c wrapper MCP config warning
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗