claude-debugs-for-you MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Language-agnostic — any VS Code-supported debugger works
Tools: set/remove breakpoints, continue, step, evaluate expressions, list stack
stdio or SSE transport from VS Code extension to MCP client
Works with Claude Desktop, Continue, Cursor
Requires a valid .vscode/launch.json

라이브 데모

실제 사용 모습

claude-debugs-for-you.replay ▶ 준비됨

0/0

설치

클라이언트 선택

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

{
  "mcpServers": {
    "claude-debugs-for-you": {
      "command": "npx",
      "args": [
        "-y",
        "claude-debugs-for-you"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

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

{
  "mcpServers": {
    "claude-debugs-for-you": {
      "command": "npx",
      "args": [
        "-y",
        "claude-debugs-for-you"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-debugs-for-you": {
      "command": "npx",
      "args": [
        "-y",
        "claude-debugs-for-you"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-debugs-for-you": {
      "command": "npx",
      "args": [
        "-y",
        "claude-debugs-for-you"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-debugs-for-you",
      "command": "npx",
      "args": [
        "-y",
        "claude-debugs-for-you"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-debugs-for-you": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "claude-debugs-for-you"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add claude-debugs-for-you -- npx -y claude-debugs-for-you

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: claude-debugs-for-you

Let Claude drive the debugger to narrow down a bug

👤 Devs stuck on a non-obvious bug ⏱ ~20 min intermediate

언제 쓸까: You've been reading logs for 20 minutes. Time to let Claude set strategic breakpoints and check variable state.

사전 조건

.vscode/launch.json with a runnable config — Use ${file} for the first config so Claude can run whichever file you have open
claude-debugs-for-you extension installed — VS Code Marketplace

흐름

Start the extension server

Start the debug MCP server. Note the path it prints and paste into Claude Desktop config.✓ 복사됨

→ Extension status bar shows running
Describe the bug

My function computeTotal() returns NaN when cart has sale items. Place a breakpoint at the start, step through, and tell me where it goes wrong.✓ 복사됨

→ Breakpoint set, program runs to it, Claude inspects locals
Diagnose

Based on the values at each step, what's the root cause and what's the smallest fix?✓ 복사됨

→ Root cause + patch

결과: Bug found by Claude driving the debugger — faster than print-logging.

함정

launch.json is misconfigured and the debugger can't start — Test with F5 in VS Code first; only then let Claude drive
Claude sets too many breakpoints and slows everything to a crawl — Tell it to use conditional breakpoints where possible

함께 쓰기: git-2

Understand a complex runtime state via expression evaluation

👤 Devs reverse-engineering unfamiliar code ⏱ ~15 min intermediate

언제 쓸까: Code works but you don't know why. Set a breakpoint at a key line and ask Claude to explore the state.

흐름

Pause

Set a breakpoint at line X, run the test, and when paused tell me what's in scope.✓ 복사됨

→ Scope dump
Evaluate

Evaluate this.store.getState().users.filter(u => u.active).length. Then show me this.config.✓ 복사됨

→ Eval results

결과: Live exploration without writing test code.

함정

Eval with side effects mutates state — Stick to read-only expressions unless you intend mutation

조합

다른 MCP와 조합해 10배 효율

claude-debugs-for-you + git-2

Debug → fix → commit loop

Debug the failing test, apply the fix you propose, then commit with a message describing what was wrong.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
set_breakpoint	file, line, condition?	Before/during a debug session	free
remove_breakpoint	id	Clean up between sessions	free
continue		Resume; returns next pause info	free
step_over		Single-step without entering functions	free
evaluate	expression: str	Inspect values at current pause point	free
get_stack		See call chain	free

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Small per call; aggregate over a session can be 10-50k if you explore a lot of state
금액: Free, MIT
팁: Ask Claude to form a hypothesis first, then verify with targeted breakpoints — avoids aimless stepping.

보안

권한, 시크릿, 파급범위

자격 증명 저장: None

데이터 외부 송신: Local debugger; values shipped to your LLM provider

절대 부여 금지: Arbitrary `evaluate` on production databases via a debugger session

Evaluation can have side effects depending on the expression — treat with the care you'd give eval().
Don't run against production processes; use reproducible local environments.

문제 해결

자주 발생하는 오류와 해결

Extension doesn't start / no 'running' in status bar

Open the VS Code Developer Tools console. Usually a port-in-use issue — change port in extension settings.

Debugger fails to start

Test F5 manually first. Ensure first config in launch.json uses ${file}.

Claude says 'no active debug session'

You need a running program. Ask Claude to start debug, which triggers VS Code's default config.

대안

claude-debugs-for-you 다른 것과 비교

대안	언제 쓰나	단점/장점
VS Code + Copilot chat with debug context	You already pay for Copilot and use VS Code natively	Less scriptable; tied to Copilot's model

claude-debugs-for-you