Spec Workflow MCP — ユースケース, インストール & ライブデモ

Name: Spec Workflow MCP Server
Author: Pimzino

なぜ使うのか

主な機能

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

ライブデモ

実際の動作

spec-workflow-mcp.replay ▶ 準備完了

0/0

インストール

クライアントを選択

~/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"
      ]
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

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

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

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit

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

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json

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

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json

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

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json

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

context_servers に追加。保存時に Zed がホットリロード。

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

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方： Spec Workflow

Build a feature with a spec, not a vibe prompt

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

使うタイミング： You're about to ask Claude to "add OAuth" and dread the 500-line diff that will land in one go.

前提条件

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

フロー

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?✓ コピーしました

→ 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.✓ コピーしました

→ Design doc with concrete architecture
Tasks + Execute

I approved. Break into tasks. Then execute task 1.1 — just that one, stop after.✓ コピーしました

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

結果： A feature shipped with reviewable intermediate artifacts — not a mystery diff.

注意点

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

組み合わせ： github · filesystem

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

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

使うタイミング： You need PM approval before implementation and the PM doesn't read GitHub PRs.

前提条件

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

フロー

Spec

Draft the requirements doc for checkout-v2 and share the dashboard URL.✓ コピーしました

→ Doc + shareable link
Iterate via feedback

PM left 3 revision comments in the dashboard. Fetch them and revise the doc.✓ コピーしました

→ Doc updated with revision history visible
Execute post-approval

Approval just went through — proceed to design.✓ コピーしました

→ Next stage starts; approval timestamp logged

結果： Traceable approval chain from non-engineer stakeholders.

注意点

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

組み合わせ： github

組み合わせ

他のMCPと組み合わせて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.✓ コピーしました

spec-workflow-mcp + filesystem

Store specs in-repo alongside code

Save the approved spec to /docs/specs/oauth-login.md and commit.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング	コスト
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

コストと制限

運用コスト

APIクォータ: Local
呼び出しあたりのトークン: Proportional to doc/task size
金額: Free
ヒント: Keep requirements concise — the approval cost is human time, not tokens

セキュリティ

権限、シークレット、影響範囲

最小スコープ： filesystem-write (for spec docs)

認証情報の保管： None

データ送信先： None — localhost dashboard

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

トラブルシューティング

よくあるエラーと対処法

Dashboard won't load

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

確認： Visit localhost:5000

Port 5000 already in use (macOS AirPlay)

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

確認： Check with `lsof -i :5000`

Tasks stay in pending after approval

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

代替案

Spec Workflow 他との比較

代替案	代わりに使う場面	トレードオフ
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

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る