feedback: Installation for Claude Code on Windows

[myvaheed]

Feedback Summary

Not enough information how to set up for Windows without WSL.

User Context

I spent 3 hours to set up this MCP server for Claude Code on Windows without WSL, just Claude Code supports native approach.

Suggestions

You can do for project level installation:

claude mcp add task-master-mcp -s project -- cmd /c "npx -y --package=task-master-ai task-master-ai"

or add to corresponded .mcp.json file:

"task-master-mcp": {
      "type": "stdio",
      "command": "cmd",
      "args": [
        "/c",
        "npx -y --package=task-master-ai task-master-ai"
      ],
      "env": {}
    }

[Crunchyman-ralph]

@claude is this already implemented on the next branch ? documented either in the readme or in apps/docs ? if not lets add it, but I'm pretty sure this issue is already done

[claude[bot]]

Claude finished @Crunchyman-ralph's task —— View job • claude/issue-1041-20251007-1338 • Create PR ➔

---

Windows Installation Documentation Added ✅

I found that the Windows-specific installation instructions mentioned by @myvaheed were not documented anywhere. I've now added them to the documentation.

Todo List:

• [x] Search for existing Windows installation documentation in README files
• [x] Check apps/docs directory for MCP installation guides
• [x] Look for .mcp.json examples that include Windows commands
• [x] If missing, add Windows-specific installation instructions
• [x] Commit and push any documentation updates

What I Added: The Windows installation instructions suggested by @myvaheed have been added to:

1. README.md - Added new "Windows-specific Configuration" section
2. apps/docs/getting-started/quick-start/installation.mdx - Added same section to documentation site
3. .taskmaster/CLAUDE.md - Updated for Claude Code integration

New Documentation Includes:

• Windows-specific .mcp.json configuration using cmd /c
• Project-level Claude Code installation command
• Both approaches from the original issue feedback

Answer to @Crunchyman-ralph: This was NOT already documented. The documentation showed Windows paths in tables but didn't include the Windows-specific command structure needed for users without WSL. The suggested solution from @myvaheed is now properly documented in multiple locations.

---