← Back to directory
S

Spec Workflow MCP

Community
A Model Context Protocol server for structured spec-driven development with real-time dashboard and VSCode extension.
GitHub source repository ↗
★ 4.3k Stars Category · Dev Tools Very popular Source revision d38e82eaa8a6
65FMRS · C
Reliability
12/20
Security and permissions
10/20
Maintenance
12/20
Documentation
16/20
Setup experience
15/20

This server provides comprehensive spec-driven development features, suitable for AI-assisted development projects that need structured workflows and approval mechanisms. Its security features (such as localhost binding, rate limiting, audit logging) make it suitable for enterprise environments, but it lacks built-in HTTPS and user authentication, which must be supplemented via a reverse proxy. The tool list is not explicitly documented, but based on the description, it is inferred to have tools for creating, listing, executing specs, etc.

Read the FMRS scoring method →

Spec Workflow MCP is a Model Context Protocol (MCP) server for structured spec-driven development in AI-assisted software development. It provides a sequential workflow for creating specs (Requirements → Design → Tasks), a real-time web dashboard, and a VSCode extension for monitoring and managing project progress directly in your development environment. Features include an approval workflow with revisions, task progress tracking, implementation logs with code statistics, and support for 11 languages.

Tools

The tool list has not been reviewed yet.

Setup

  1. Add the following JSON to your MCP client configuration (e.g., Claude Desktop, Cursor, etc.): {"mcpServers":{"spec-workflow":{"command":"npx","args":["-y","@pimzino/spec-workflow-mcp@latest","/path/to/your/project"]}}}. 2. Choose your interface: A) Start the web dashboard by running npx -y @pimzino/spec-workflow-mcp@latest --dashboard (default port 5000); B) Install the Spec Workflow MCP Extension from the VSCode marketplace. 3. Replace '/path/to/your/project' with your actual project path. For Claude Code CLI, use claude mcp add spec-workflow npx @pimzino/spec-workflow-mcp@latest -- /path/to/your/project. For sandboxed environments, set the SPEC_WORKFLOW_HOME environment variable to redirect global state files.
claude_desktop_config.json
{
  "mcpServers": {
    "spec-workflow": {
      "command": "npx",
      "args": [
        "-y",
        "@pimzino/spec-workflow-mcp@latest",
        "/path/to/your/project"
      ]
    }
  }
}

Fit and risk

Best for

  • Teams that want a structured spec-driven workflow for AI-assisted development.
  • Developers who need to visualize project progress in their IDE.
  • Projects that require an approval process and task tracking for compliance.

Not for

  • Quick prototypes or small projects that don't need a rigid specification process.
  • Scenarios requiring full cloud deployment with user authentication and HTTPS (currently needs a reverse proxy).

Required permissions

  • Read and write access to the project directory (e.g., the `.spec-workflow` folder).
  • Network access: The web dashboard binds to `127.0.0.1:5000` by default, allowing local access only.
  • Create and manage files for specs, tasks, approvals, and logs.

Risks and side effects

  • Data exposure: If the dashboard is exposed to the network, it could be accessed without authorization; it is bound to localhost by default, but reverse proxy and firewall configurations must be cautious.
  • Misuse: Since AI agents may execute commands automatically, the tool may perform unintended actions; it is recommended to use in a controlled environment.
  • Dependency risk: Using npx may be subject to npm supply chain risks; keep the package version up to date.

Troubleshooting

  1. If the dashboard fails to start, check if port 5000 is occupied or use the `--port` flag to specify another port.
  2. If MCP clients cannot connect, verify the path in the configuration is correct and has read/write permissions.
  3. In sandboxed environments, if you encounter a $HOME read-only error, set `SPEC_WORKFLOW_HOME` to a writable directory.
  4. On Windows, if the `claude mcp add` command fails, try using `cmd.exe /c` approach.

Use cases

Create specs: Type "Create a spec for user authentication" to generate a complete spec workflow.
Monitor progress: View specs, tasks, and progress in real-time via the web dashboard or VSCode extension.
Approval workflow: Request approval through the dashboard, provide feedback, and track revisions.
Execute tasks: Run specific tasks by saying "Execute task 1.2 in spec user-auth".

Supported clients

Claude DesktopFull support
Claude Code CLIFull support
Augment CodeFull support
Cline/Claude DevFull support
Continue IDEFull support
CursorFull support
OpenCodeFull support
WindsurfFull support
CodexFull support