spec-workflow-mcp
Spec Workflow MCP is a Model Context Protocol server for structured spec-driven development. Work proceeds through sequential documents (requirements, then design, then tasks), with an approval system in which documents are created, approval is requested through the dashboard, feedback is given and revisions are tracked. A real-time web dashboard shows specs, task progress with progress bars, and searchable implementation logs with code statistics, and a VS Code extension offers the same dashboard in the sidebar. The README is available in 11 languages.
Setup is two steps: add the server to your AI tool's MCP configuration with `npx -y @pimzino/spec-workflow-mcp@latest /path/to/your/project`, then choose an interface. The web dashboard (required for CLI users) starts with `npx -y @pimzino/spec-workflow-mcp@latest --dashboard` on port 5000, and one dashboard instance serves all your projects; VS Code users can install the extension instead. You then ask the assistant things like "Create a spec for user authentication", "List my specs" or "Execute task 1.2 in spec user-auth". Client-specific setup is documented for tools such as Augment Code. GitHub shows the licence as GPL.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-07-03
- Commits, last 90 days
- 0
- Releases, last 90 days
- 0
- Latest release
- —
- Open issues
- 11
- Recent issues with at least one comment
- 15/24
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #237 [Bug]: MCP server / client in langflow showing "Error loading server: Connection closed"1 comments · 2026-09-05
- #236 [Feature]: list of feature requests + minor bug reports0 comments · 2026-08-31
- #234 MCP spec conformance: 10 requirement(s) violated (via @hasmcp/mcp-spec-test)0 comments · 2026-08-24
- #232 [Feature]: Review implementation discoveries before task completion0 comments · 2026-08-18
- #230 Consider replacing TOON with GCF for tool response encoding0 comments · 2026-06-18
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!