SkillFoxx

Type a name, a task or a service

Spec Workflow MCP

MCP server for spec-driven development: requirements, design and tasks step by step, with a web dashboard and a VS Code extension

MCP server

Medium risk

We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.

Why this level

  • Creates and edits spec files in the project
  • Runs a local web dashboard for approvals
  • Reads project contents to plan tasks
All reasons and checks

pimzino/spec-workflow-mcpAuthor:Pimzino

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/spec-workflow-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

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

Or add to the file .mcp.json, in the project

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

If the file already exists, add the server inside the mcpServers key.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

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

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

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

Or add to the file .vscode/mcp.json, in the project

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

If the file already exists, add the server inside the servers key.

Run in a terminal

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

Or add to the file ~/.codex/config.toml, for all projects

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

If the file already exists, append the block to the end.

Add to the file ~/.gemini/settings.json, for all projects

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

If the file already exists, add the server inside the mcpServers key.

Add to the file ~/.config/devin/mcp_config.json, for all projects

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

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

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

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Add to the file .roo/mcp.json, in the project

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

If the file already exists, add the server inside the mcpServers key.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

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

If the file already exists, add the server inside the mcp key.

Add to the file ~/.config/zed/settings.json, for all projects

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

If the file already exists, add the server inside the context_servers key.

Add to the file .codeassistant/mcp.json, in the project

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

If the file already exists, add the server inside the mcpServers key.

You will need: Node.js

Checked against the repository on Sep 24, 2026, commit d38e82e.

Text for your agent

Add the MCP server: claude mcp add spec-workflow npx @pimzino/spec-workflow-mcp@latest -- /path/to/project. Then start the dashboard: npx -y @pimzino/spec-workflow-mcp@latest --dashboard.

Other ways from the author
claude mcp add spec-workflow npx @pimzino/spec-workflow-mcp@latest -- /path/to/your/project

Replace the path with your project directory. The -- separator passes the path to the script, not to npx.

This is third-party code. Review the repository files before installing.

What it does

The server sets a structured, spec-driven development process: requirements first, then design, then tasks. The agent creates and maintains these documents right inside the project, while a web dashboard and a VS Code extension show specs, statuses and progress in real time. An approval flow is built in: a document is sent for approval, the author leaves feedback, and revisions are tracked. There is a task progress tracker with progress bars and a searchable implementation log with code statistics. You work in natural language, for example asking it to create a spec or run a specific task, and the interface is translated into several languages, including Russian.

Who it is for. For developers, product and project managers who want to run development against clear specs.

Good fit when

  • You want to turn an idea into a spec step by step: requirements, design, tasks
  • You want to approve documents and track feedback and revisions
  • You want to see spec status and task progress in a dashboard

Not a fit when

  • You need a quick one-off task without a spec structure
  • You cannot run the local dashboard and do not use the VS Code extension

Example request

Create a spec for password login: requirements, design and tasks, and send it for approval

Limitations

Approving documents needs a running web dashboard or the VS Code extension, and the dashboard listens on port 5000 by default. It needs Node.js and npm access to run via npx. At the time of writing the author announced a temporary pause in development. The license is GPL-3.0, which matters when embedding.

How to disable. Remove the spec-workflow block from your MCP configuration and stop the dashboard. Uninstall the extension from VS Code the usual way.

MCP

Transport
stdio
Authentication
not required

Security check

  • Creates and edits spec files in the project
  • Runs a local web dashboard for approvals
  • Reads project contents to plan tasks

README in short

The README describes an MCP server for spec-driven development with sequential creation of requirements, design and task documents. It highlights the approval flow, a task tracker with progress bars, an implementation log and a real-time web dashboard, plus a VS Code extension. Installation runs through npx with a project path, and the dashboard starts with a separate command on port 5000. Ready configurations are given for many clients along with a Docker option. The interface is available in 11 languages, including Russian, under a GPL-3.0 license.

FAQ

Do I have to run the dashboard?

Approving documents needs either the web dashboard or the VS Code extension. The dashboard runs with a separate --dashboard command, and one instance serves all projects.

Which clients does it work with?

The README documents setup for Claude Code, Claude Desktop, Cursor, Windsurf, Cline, Continue, OpenCode, Codex and Augment via MCP configuration.

Editors’ pick

A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review

PluginMedium riskNo VPN needed292.5K
Editors’ pick

Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture

SkillLow risk271.4K
Editors’ pick

GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation

CLIMedium riskNo VPN needed139.3K

Reference MCP servers

Model Context Protocol servers

Official

Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything

MCP serverMedium risk90.6K
Foxx AISpec Workflow MCP

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.