claude-debugs-for-you MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

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

Demo ao vivo

Como fica na prática

claude-debugs-for-you.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

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

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: claude-debugs-for-you

Let Claude drive the debugger to narrow down a bug

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

Quando usar: You've been reading logs for 20 minutes. Time to let Claude set strategic breakpoints and check variable state.

Pré-requisitos

.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

Fluxo

Start the extension server

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

→ 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.✓ Copiado

→ 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?✓ Copiado

→ Root cause + patch

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

Armadilhas

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

Combine com: git-2

Understand a complex runtime state via expression evaluation

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

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

Fluxo

Pause

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

→ Scope dump
Evaluate

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

→ Eval results

Resultado: Live exploration without writing test code.

Armadilhas

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

Combinações

Combine com outros MCPs para 10× de alavancagem

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.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
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

Custo e limites

O que custa rodar

Cota de API: None
Tokens por chamada: Small per call; aggregate over a session can be 10-50k if you explore a lot of state
Monetário: Free, MIT
Dica: Ask Claude to form a hypothesis first, then verify with targeted breakpoints — avoids aimless stepping.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: None

Saída de dados: Local debugger; values shipped to your LLM provider

Nunca conceda: 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.