# Spec Workflow MCP — Spec-Driven Dev Dashboard > Spec Workflow MCP is an MCP server for spec-driven development with a dashboard and VS Code extension; verified 4,170★ and supports 11 languages. ## Install Merge the JSON below into your `.mcp.json`: ## Quick Use ```bash # Add to your MCP client config: # command: npx # args: ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"] npx -y @pimzino/spec-workflow-mcp@latest --dashboard ``` ## Intro Spec Workflow MCP is an MCP server for spec-driven development with a dashboard and VS Code extension; verified 4,170★ and supports 11 languages. **Best for:** Spec-first agent coding with approvals, progress tracking, and an auditable workflow **Works with:** MCP clients (npx stdio) plus optional VS Code extension and web dashboard **Setup time:** 5-15 minutes ### Key facts (verified) - GitHub: 4170 stars · 344 forks · pushed 2026-05-05. - License: GPL-3.0 · owner avatar + repo URL verified via GitHub API. - README-backed entrypoint: `npx -y @pimzino/spec-workflow-mcp@latest /path/to/your/project`. ## Main - Use the sequential spec flow the README describes (Requirements → Design → Tasks) to keep agent work bounded and reviewable. - Treat approvals as a gate: request review via the dashboard, capture revisions, then let the agent implement the next approved task only. - Set a dedicated home directory when needed (README shows `SPEC_WORKFLOW_HOME=...`) so workflow state stays in-repo and auditable. ### Source-backed notes - README positions it as an MCP server for structured spec-driven development with a real-time dashboard and a VS Code extension. - README lists key features like approval workflow, task progress tracking, and implementation logs with code statistics. - README lists multi-language support and explicitly states it’s available in 11 languages. ### FAQ - **Do I need the VS Code extension?**: No—the MCP server + web dashboard work without it; the extension is an optional UX. - **Where is the workflow data stored?**: Configure a home directory (e.g., `SPEC_WORKFLOW_HOME`) so state lives where you expect. - **What’s the minimal way to start?**: Run `npx -y ... /path/to/project` as an MCP server and open the dashboard to create your first spec. ## Source & Thanks > Source: https://github.com/Pimzino/spec-workflow-mcp > License: GPL-3.0 > GitHub: ⭐ 4170 · forks 344 Thanks to the upstream maintainers for shipping the original project. --- ## 快速使用 ```bash # Add to your MCP client config: # command: npx # args: ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"] npx -y @pimzino/spec-workflow-mcp@latest --dashboard ``` ## 简介 Spec Workflow MCP 是面向 spec-driven 开发的 MCP server,带实时 Dashboard 与 VS Code 扩展;已验证 4,170★,并支持 11 种语言界面。 **适合谁用:** 用规格驱动的方式做 agent 编程,并需要审批、进度追踪与可审计工作流 **适用环境:** 支持 MCP 的客户端(npx stdio),并可选配 VS Code 扩展与 Web Dashboard **配置耗时:** 5-15 minutes ### 关键事实(已验证) - GitHub:4170 stars · 344 forks;最近更新 2026-05-05。 - 许可证:GPL-3.0;作者头像与仓库链接均已通过 GitHub API 复核。 - README 中可对照的入口命令:`npx -y @pimzino/spec-workflow-mcp@latest /path/to/your/project`。 ## 正文 - 按 README 的顺序做规格(Requirements → Design → Tasks),让 agent 的工作范围更可控、可评审。 - 把审批当作门禁:在 Dashboard 里发起审批、记录修订,然后只让 agent 实现下一条“已批准任务”。 - 需要时指定专用目录(README 示例 `SPEC_WORKFLOW_HOME=...`),让工作流状态可追溯并与项目绑定。 ### 基于来源的要点 - README 将其定位为 spec-driven 开发的 MCP server,包含实时 Dashboard 与 VS Code 扩展。 - README 列出能力:审批工作流、任务进度追踪、实现日志与代码统计等。 - README 明确写到支持 11 种语言界面。 ### 常见问题 - **必须装 VS Code 扩展吗?**:不必须。MCP server + Web Dashboard 可独立工作;扩展是可选体验优化。 - **工作流数据存在哪里?**:可通过 `SPEC_WORKFLOW_HOME` 等方式指定目录,确保状态落在你期望的位置。 - **最小上手路径?**:以 MCP server 方式运行 `npx -y ... /path/to/project`,打开 Dashboard 创建第一份 spec。 ## 来源与感谢 > Source: https://github.com/Pimzino/spec-workflow-mcp > License: GPL-3.0 > GitHub: ⭐ 4170 · forks 344 --- Source: https://tokrepo.com/en/workflows/spec-workflow-mcp-spec-driven-dev-dashboard Author: MCP Hub