hwanyong/mcp-debug-tools
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
VSCode extension and CLI tool for MCP-based debugging with DAP protocol support
Обзор
— Let your AI assistant set breakpoints, step through code, and inspect variables in real-time. Traditional AI coding assistants can and code, but they can't it. MCP Debug Tools removes this limitation by giving AI agents direct access to VS Code's debugger through simple CLI commands. Beyond the standard MCP proxy, you can execute debugging actions via — no persistent connection required. - : Shell-based AI agents interact with the debugger directly - : No need to configure or maintain an MCP server connection - : Results in pure JSON (stdout), logs separated to stderr — AI parses instantly - : Integrate VS Code debugging into automated bash scripts seamlessly The extension now into your workspace when activated, so AI agents can discover and use debugging tools . Run the CLI directly from the VS Code extension's install path — . All are now fully documented in the auto-injected skill file, organized by category with parameters and usage examples. Currently in beta testing.
README
Показан фрагмент оригинального README. Открыть оригинал.
MCP Debug Tools
The bridge between AI Agents and VS Code Debugger — Let your AI assistant set breakpoints, step through code, and inspect variables in real-time.
Why MCP Debug Tools?
Traditional AI coding assistants can read and write code, but they can’t debug it. MCP Debug Tools removes this limitation by giving AI agents direct access to VS Code’s debugger through simple CLI commands.
| Without MCP Debug Tools | With MCP Debug Tools |
|---|---|
| AI guesses at bugs from code reading | AI sets breakpoints and inspects live runtime state |
| “Try adding a console.log here” | AI steps through code line-by-line automatically |
| Manual copy-paste of error messages | AI reads call stacks and variable values as JSON |
💡 Direct CLI Control — Works Without MCP Connection
Beyond the standard MCP proxy, you can execute debugging actions via one-off terminal commands — no persistent connection required.
- Terminal AI Friendly: Shell-based AI agents interact with the debugger directly
- Zero Connection Overhead: No need to configure or maintain an MCP server connection
- Easy Parsing: Results in pure JSON (
stdout), logs separated tostderr— AI parses instantly - Scriptable: Integrate VS Code debugging into automated bash scripts seamlessly
# Discover all available tools
npx @uhd_kr/mcp-debug-tools list
# Execute tools directly
npx @uhd_kr/mcp-debug-tools call add-breakpoint '{"file": "src/app.ts", "line": 15}'
npx @uhd_kr/mcp-debug-tools call step-over
🚀 What’s New in v1.0.0
🤖 AI Agent Skill Auto-Injection
The extension now automatically injects skill documents into your workspace when activated, so AI agents can discover and use debugging tools without any manual configuration.
| AI Platform | Auto-detected Path | Status |
|---|---|---|
| Gemini (Google) | .gemini/skills/dap-cli-debugging/SKILL.md |
✅ Supported |
| Claude Code (Anthropic) | .claude/skills/dap-cli-debugging/SKILL.md |
✅ Supported |
🔌 Offline CLI Support
Run the CLI directly from the VS Code extension’s install path — no internet or npx required.
# macOS / Linux
node ~/.vscode/extensions/uhd.mcp-debug-tools-*/out/cli.js call get-active-session
# Windows (PowerShell)
node "$env:USERPROFILE\.vscode\extensions\uhd.mcp-debug-tools-*\out\cli.js" call get-active-session
📖 Comprehensive Tool Documentation
All 29 debugging tools are now fully documented in the auto-injected skill file, organized by category with parameters and usage examples.
⚠️ Beta Testing
Установка
npx -y @uhd_kr/mcp-debug-tools@latestКонфигурация
{
"mcpServers": {
"dap-proxy": {
"command": "npx",
"args": ["-y", "@uhd_kr/mcp-debug-tools@latest"],
"env": {}
}
}
}