Spec Workflow MCP

What it does

• Spec-driven development MCP: walks Claude through requirements → design → tasks → implementation
• Web dashboard (port 5000) for reviewing/approving specs and tracking task progress
• Stores specs as markdown under `.spec-workflow/` in your project

When to use it

For larger features where you want structured artifacts before code: Claude drafts requirements/design/tasks docs, you approve in the dashboard, then implementation follows the spec.

Getting started

{
  "spec-workflow": {
    "command": "npx",
    "args": ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"]
  }
}

Start the optional dashboard (port 5000) for approvals — required for CLI-only users who want the review UI.

Things to know

The project path is a positional arg — point it at the repo root or specs land in the wrong directory. Dashboard is a separate process to keep running.