5 phút đọc
microsoft/DebugMCP: Gift your VS Code agent a real debugger: breakpoints, stepping, inspection. – Repository microsoft/DebugMCP. Mô tả: Gift your VS Code agent a real debugger: breakpoints, stepping, inspection.. 539 stars, 61 forks, ngôn ngữ chính TypeScript, cập nhật 2026-10-03.
1. Repository làm gì?
Let AI agents debug your code inside VS Code – set breakpoints, step through execution, inspect variables, and evaluate expressions. Works with Codex, GitHub Copilot, GitHub Copilot CLI, Claude Code, Cline, Cursor, Windsurf, Roo Code, and any MCP-compatible assistant. Compatible with any VS Code supported coding language.
🚀 DebugMCP CLI is now available on npm! Debug directly from the terminal without requiring VS Code or any IDE at all by connecting AI coding agents to explicitly configured Debug Adapter Protocol (DAP) adapters. The debug adapter and target process run in the background. Install it with npm install –global debugmcp, then run debugmcp configure –agent copilot-cli. The CLI also installs the debug-live skill automatically. View the package on npm
⭐ If you find DebugMCP useful, please star the repo on GitHub! It helps others discover the project and motivates continued development.
📢 Developers Notice: This extension is maintained by ozzafar@microsoft.com and orbarila@microsoft.com. We welcome feedback and contributions to help improve this extension.
🎬 Watch DebugMCP in action — your AI assistant autonomously sets breakpoints, steps through code, and inspects variables directly in VS Code.
Install DebugMCP from VS Code Marketplace or use the direct link: vscode:extension/ozzafar.debugmcpextension
2. Dữ liệu và cấu trúc đáng chú ý
Install DebugMCP from Open VSX Registry
DebugMCP is an MCP server that gives AI coding agents full control over the VS Code debugger. Instead of reading logs or guessing, your AI assistant can autonomously set breakpoints, launch debug sessions, step through code line by line, inspect variable values, and evaluate expressions — just like a human developer would. It runs 100% locally, requires zero configuration, and works out of the box with any MCP-compatible AI assistant.
Note: The MCP server exposes tools for debugger actions, while the procedural workflow guidance (when to debug, how to structure a root-cause investigation, language-specific quirks) lives in the companion Agent Skill. Tool descriptions stay terse and behavioral; the extension installs the debug-live skill into the standard skills directories (~/.agents/skills/, plus ~/.copilot/skills/ when present) so skills-compatible harnesses load the full workflow on demand. The server also advertises MCP instructions pointing agents at it before debugging.
DebugMCP follows systematic debugging practices for effective issue resolution:
The standalone host talks directly to explicitly configured DAP adapters and does not require VS Code. It never discovers, downloads, installs, or selects an adapter automatically.
For repository development, build and invoke the local bundle:
Adapter registrations are stored in .debugmcp.json by default. Add –user to adapter add, adapter list, or adapter remove to use the per-user configuration. Project registrations override registrations with the same name in user configuration.
3. Khả năng ứng dụng và giới hạn
Language shorthands derive the DAP type and file extensions for python, csharp, dotnet, cpp, c, javascript, typescript, node, java, go, rust, ruby, php, swift, and dart. These are configuration conveniences, not a language support boundary. The command remains explicit so the selected environment determines which adapter installation is used. Languages without a shorthand provide –type and –extensions explicitly. Compiled-language registrations can provide the executable in –launch; values support ${workspaceFolder}, ${file}, ${fileDirname}, and ${fileBasenameNoExtension}.
The current CLI supports adapters that speak DAP over stdio. A registration can provide adapter-specific launch properties with –launch followed by a JSON object. If multiple registered adapters claim the same file extension, start_debugging.configurationName must identify the adapter to use. Test discovery remains host-specific; configure the adapter launch properties to run the required test command.
Adapter arguments beginning with — can follow –args directly. Use a standalone — after –args when an adapter argument has the same name as a DebugMCP option, for example –args — –user.
debugmcp configure presents the same agent choices as the VS Code extension's setup popup and writes the standalone stdio command for every selected agent. In automation, repeat –agent to bypass the terminal prompt, for example debugmcp configure –agent copilot-cli –agent codex. Each configuration has one canonical debugmcp entry, so configuring the CLI replaces an existing extension HTTP entry rather than registering both. The command also installs the bundled debug-live skill into the standard personal skills directories. Restart configured agents to discover it.
Use debugmcp status to inspect the GitHub Copilot CLI registration. The DebugMCP command configures only the standalone CLI. To use the interactive VS Code version, configure it through the DebugMCP extension's agent popup; the command line does not select or configure the extension.
Option 1: Direct Link (Fastest)
After installation, you should see:
📝 Note: No additional debugging rule instructions are needed – the extension works out of the box.
💡 Tip: Enable auto-approval for all debugmcp tools in your AI assistant to create seamless debugging workflows without constant approval interruptions.
Số liệu repository có thể thay đổi; nên mở liên kết nguồn để kiểm tra README, giấy phép và trạng thái phát hành.
Nguồn tham khảo: Xem bài gốc
