Debug Adapter Protocol MCP Server
Debug Adapter Protocol (DAP) MCP server enabling AI agents to control debuggers via the Debug Adapter Protocol — setting breakpoints, stepping through code, inspecting variables, evaluating expressions in debug context, and integrating AI-assisted debugging into development workflows. Supports any DAP-compatible debugger (VS Code debug adapters, gdb, lldb, etc.).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Local debugger only. No credentials. Full program memory access — use only in development environments. Never debug production with AI-initiated sessions.
⚡ Reliability
Best When
A developer wants AI assistance with interactive debugging — the AI can systematically set breakpoints, step through code, and inspect state to help identify bugs.
Avoid When
You rely on unit tests and logging rather than interactive debugging, or need production-safe analysis tools.
Use Cases
- • Setting breakpoints and stepping through code from AI debugging agents
- • Inspecting variable state at runtime from code analysis agents
- • Evaluating expressions in debug context from diagnostic agents
- • Automating debug session setup and teardown from DevOps agents
- • AI-assisted root cause analysis through systematic code stepping from debugging agents
- • Capturing runtime state snapshots for bug reporting from QA agents
Not For
- • Production debugging (DAP debugging is for development environments)
- • High-performance profiling (use profiling tools, not debugger stepping)
- • Teams not doing interactive debugging — test-based development may not need this
Interface
Authentication
No authentication — connects to local DAP-compatible debug adapter. Debug adapter must be running and configured for the target language/runtime.
Pricing
Free open source DAP MCP server. Debug adapters are also typically free (VS Code extensions).
Agent Metadata
Known Gotchas
- ⚠ DAP debug adapter must be running and configured — setup varies significantly by language
- ⚠ Debug session state is ephemeral — breakpoints cleared when debuggee terminates
- ⚠ Stepping through code is slow for AI to navigate long call chains — use targeted breakpoints
- ⚠ Variable inspection serialization may truncate large objects — configure depth limits
- ⚠ Community MCP — DAP protocol is complex; not all DAP features may be exposed via MCP
- ⚠ Process must be launched in debug mode — cannot attach to arbitrary production processes
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Debug Adapter Protocol MCP Server.
Scores are editorial opinions as of 2026-03-06.