Spec Workflow MCP

listing.by

Run a spec-driven development workflow (requirements, design, tasks) with approvals and a live web dashboard.

state.local.long (state.local.title)listing.badge.runs_with

listing.install

listing.local.explain

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

listing.local.needs listing.local.note

act.add_to a11y.new_tabact.add_to a11y.new_tab

listing.share.h

listing.share.p_local

mcp.tc/i/spec-workflow

listing.about

Spec Workflow guides AI-assisted development through sequential specs: requirements, then design, then tasks. It includes an approval process with revisions, task progress tracking and searchable implementation logs. Progress can be monitored in a real-time web dashboard or in a VSCode extension.

It runs locally over stdio with npx and takes the project path as an argument. No sign-in or API key is needed. The dashboard is started separately with the --dashboard flag and listens on port 5000 on localhost by default. A Docker setup for the dashboard is also provided.

listing.can

  • Create specs in sequence: requirements, design, tasks
  • Request and track document approvals with revisions
  • List specs and show their status
  • Execute individual tasks from a spec
  • Track task progress in a live web dashboard
  • Search implementation logs of completed tasks

listing.tools

listing.notools.local

listing.prompts

  • Create a spec for user authentication

  • List my specs

  • Execute task 1.2 in spec user-auth

  • Show the status of the user-auth spec

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio spec-workflow -- npx -y @pimzino/spec-workflow-mcp@latest /path/to/project
  1. Start Claude Code and type /mcp. spec-workflow should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "spec-workflow": {
      "command": "npx",
      "args": [
        "-y",
        "@pimzino/spec-workflow-mcp@latest",
        "/path/to/project"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Needs Node.js on your computer.

VS Code

Install in VS Code a11y.new_tab

Or from a terminal:

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

Or commit it to the repo in .vscode/mcp.json:

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

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "spec-workflow": {
      "command": "npx",
      "args": [
        "-y",
        "@pimzino/spec-workflow-mcp@latest",
        "/path/to/project"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

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

Or edit ~/.codex/config.toml directly:

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

Needs Node.js on your computer.

Gemini CLI

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

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

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

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer.

listing.faq

Can I paste mcp.tc/i/spec-workflow into my MCP client?

No. Spec Workflow MCP runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @pimzino/spec-workflow-mcp@latest /path/to/project.

Does Spec Workflow MCP need an API key?

No. It doesn't declare any keys or environment variables. It runs with your user account's permissions, so check what its tools can reach.

Is Spec Workflow MCP a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @pimzino/spec-workflow-mcp@latest /path/to/project, which needs Node.js.

What can Spec Workflow MCP do?

You can create specs in sequence: requirements, design, tasks, request and track document approvals with revisions and list specs and show their status.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read Spec Workflow MCP's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Spec Workflow MCP on mcp.tc](https://mcp.tc/i/spec-workflow/badge.svg)](https://mcp.tc/i/spec-workflow)
HTML
<a href="https://mcp.tc/i/spec-workflow"><img src="https://mcp.tc/i/spec-workflow/badge.svg" alt="Spec Workflow MCP on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/spec-workflow.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/spec-workflow" title="Spec Workflow MCP on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/spec-workflow.json

listing.em.fields

listing.related

listing.more_in

  • iOS Simulator MCP

    Joshua Yoes

    state.local.label (state.local.title)

    Inspect the UI, tap, type, swipe, take screenshots and record video in the iOS Simulator from your assistant.

    mcp.tc/i/ios-simulator

  • Laravel Boost

    Laravel

    state.local.label (state.local.title)

    Give AI agents Laravel-aware context and version-specific docs search while working on a local Laravel app.

    mcp.tc/i/laravel-boost

  • MobileBuildMCP

    Sentry

    state.local.label (state.local.title)

    Build, run, test and debug iOS and macOS apps with Xcode and the Simulator from an AI agent.

    mcp.tc/i/mobilebuildmcp

  • Next.js DevToolsvf.sr

    Vercel

    state.local.label (state.local.title)

    Query a running Next.js dev server for runtime errors, routes and logs, and find version-matched docs from your coding agent.

    mcp.tc/i/nextjs-devtools

  • Mobile MCP

    Mobile Next

    state.local.label (state.local.title)

    Automate iOS and Android simulators, emulators and real devices: tap, swipe, type, take screenshots and read the accessibility tree.

    mcp.tc/i/mobile-mcp

  • shadcn/ui

    shadcn

    state.local.label (state.local.title)

    Browse, search and install shadcn/ui components and other registry components into your project from your assistant.

    mcp.tc/i/shadcn

listing.disclaimer_checked