Spec Workflow MCP — Casos de uso, Instalar & Demo en vivo

Name: Spec Workflow MCP Server
Author: Pimzino

Por qué usarlo

Características clave

Sequential Requirements → Design → Tasks with approval between each
Web dashboard on localhost:5000 with live updates
VSCode extension with in-IDE sidebar
11-language UI
Searchable implementation logs with code stats

Demo en vivo

Cómo se ve en la práctica

spec-workflow-mcp.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.cursor/mcp.json · .cursor/mcp.json

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

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

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

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: Spec Workflow

Build a feature with a spec, not a vibe prompt

👤 Devs shipping medium-complexity features ⏱ ~90 min intermediate

Cuándo usarlo: You're about to ask Claude to "add OAuth" and dread the 500-line diff that will land in one go.

Requisitos previos

Project path known — MCP is launched with /path/to/project as arg

Flujo

Requirements

Use spec-workflow. Create a spec named oauth-login. Start with requirements — what are we adding, who is it for, what are the non-goals?✓ Copiado

→ Requirements doc drafted, link to dashboard for approval
Approve + Design

I approved in the dashboard. Now write the design: components, data model, sequence diagram, error cases.✓ Copiado

→ Design doc with concrete architecture
Tasks + Execute

I approved. Break into tasks. Then execute task 1.1 — just that one, stop after.✓ Copiado

→ Task list created; only task 1.1 implemented with log entry

Resultado: A feature shipped with reviewable intermediate artifacts — not a mystery diff.

Errores comunes

Claude tries to skip straight to code — The MCP blocks it — but be explicit in prompts anyway: "do not implement yet"

Combinar con: github · filesystem

Get a non-engineer stakeholder to approve a spec before code happens

👤 Teams with PM/design sign-off loops ⏱ ~60 min intermediate

Cuándo usarlo: You need PM approval before implementation and the PM doesn't read GitHub PRs.

Requisitos previos

Dashboard URL shareable — Port-forward or expose localhost:5000 via ngrok for remote PMs

Flujo

Spec

Draft the requirements doc for checkout-v2 and share the dashboard URL.✓ Copiado

→ Doc + shareable link
Iterate via feedback

PM left 3 revision comments in the dashboard. Fetch them and revise the doc.✓ Copiado

→ Doc updated with revision history visible
Execute post-approval

Approval just went through — proceed to design.✓ Copiado

→ Next stage starts; approval timestamp logged

Resultado: Traceable approval chain from non-engineer stakeholders.

Errores comunes

Dashboard not reachable for remote users — Use Tailscale or ngrok with auth

Combinar con: github

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

spec-workflow-mcp + github

Open a PR per approved task

After executing task 2.1, open a GitHub PR titled "feat(oauth): task 2.1" with the diff.✓ Copiado

spec-workflow-mcp + filesystem

Store specs in-repo alongside code

Save the approved spec to /docs/specs/oauth-login.md and commit.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
create_spec	name: str	Start a new feature	free
write_requirements	spec_id, content: markdown	First phase of any spec	free
write_design	spec_id, content: markdown	After requirements approved	free
create_tasks	spec_id, tasks: []	After design approved	free
execute_task	spec_id, task_id	Implement one task at a time	free
get_approval_status	spec_id, stage	Gate next stage	free

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: Local
Tokens por llamada: Proportional to doc/task size
Monetario: Free
Consejo: Keep requirements concise — the approval cost is human time, not tokens

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: filesystem-write (for spec docs)

Almacenamiento de credenciales: None

Salida de datos: None — localhost dashboard

Don't expose localhost:5000 to the public internet without auth

Resolución de problemas

Errores comunes y soluciones

Dashboard won't load

Start it explicitly: npx -y @pimzino/spec-workflow-mcp@latest --dashboard

Verificar: Visit localhost:5000

Port 5000 already in use (macOS AirPlay)

Pass --port 5050 or disable AirPlay Receiver in System Settings

Verificar: Check with `lsof -i :5000`

Tasks stay in pending after approval

MCP client may be caching old tool results — restart the client

Alternativas

Spec Workflow vs otros

Alternativa	Cuándo usarla	Contrapartida
Plain Markdown in /docs	Solo dev with no approval loop needed	No structure enforcement, no dashboard
Linear MCP	You already use Linear for tasks and want Claude to touch issues directly	No spec-doc layer

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills