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

Spec Workflow

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

설치

클라이언트 선택

사용 사례

실전 활용법: Spec Workflow

Build a feature with a spec, not a vibe prompt

사전 조건

흐름

함정

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

사전 조건

흐름

함정

조합

다른 MCP와 조합해 10배 효율

도구

이 MCP가 노출하는 것

비용 및 제한

운영 비용

보안

권한, 시크릿, 파급범위

문제 해결

자주 발생하는 오류와 해결

대안

Spec Workflow 다른 것과 비교

더 보기

리소스