Record · spec-workfloMCP serverCosts not checkedRecord checked Sep 23, 2026

Spec Workflow MCP

Spec-driven development for AI agents: requirements, design and tasks with approvals and a live dashboard.

Visit Spec Workflow MCP →View repository

Sources and review

Checked against public documentation on September 23, 2026. Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.

Repository and README

Best for

Teams that want an agent to plan against reviewed requirements before writing code.

Avoid if

You need active maintenance; the author notes a break from the project.

About Spec Workflow MCP

Spec Workflow MCP guides an AI assistant through a sequential spec process, from requirements to design to tasks, with an approval system for reviewing and revising each document. A real-time web dashboard and a VS Code extension show specs, tasks and progress.

Spec Workflow MCP is listed in this index written primarily in TypeScript, with 4.3k stars on GitHub. Its latest recorded repository push was in July 2026; that is not an ASE editorial review date.

Before connecting: access and data

This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.

List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.

Read the setup guide →

Add Spec Workflow MCP to your MCP client

Generated from the launch command in the project's README. Your client starts the server on demand.

Claude CodeRun in your terminal

claude mcp add spec-workflow-mcp -- npx -y @pimzino/spec-workflow-mcp@latest /path/to/your/project

Cursor~/.cursor/mcp.json or .cursor/mcp.json

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

VS Code.vscode/mcp.json

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

Claude Desktopclaude_desktop_config.json

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

Codex~/.codex/config.toml

[mcp_servers.spec-workflow-mcp]
command = "npx"
args = ["-y", "@pimzino/spec-workflow-mcp@latest", "/path/to/your/project"]

Check the project's README for required accounts, keys and permissions before connecting. Setup guide for each client →

For agent buildersMake your product part of the discovery.Explore advertising