A Model Context Protocol (MCP) server that provides debugging capabilities through the Debug Adapter Protocol (DAP). This server enables AI assistants and other MCP clients to interact with debuggers for various programming languages.
The MCP DAP Server acts as a bridge between MCP clients and DAP-compatible debuggers, allowing programmatic control of debugging sessions. It provides a comprehensive set of debugging tools that can be used to:
- Start and stop debugging sessions
- Set breakpoints (line-based and function-based)
- Control program execution (continue, step in/out/over, pause)
- Inspect program state (threads, stack traces, variables, scopes)
- Evaluate expressions
- Attach to running processes
- Handle exceptions
- Basic demo with multiple prompts
- Autonomous agentic debugging pt.1
- Autonomous agentic debugging pt.2
- Unified Debug Launch: Single
debugtool handles source, binary, and attach modes - Automatic Context: Execution control tools return full state (location, stack, variables)
- Streamlined API: 13 tools cover all debugging operations
- Breakpoint Management: Set line and function breakpoints, run-to-cursor
- Full State Inspection: Stack traces, scopes, and variables in one call
- Expression Evaluation: Evaluate and modify variables in context
- Process Attachment: Attach to running processes
- Disassembly Support: View disassembled code at memory addresses
- Go 1.24.4 or later
- A DAP-compatible debugger for your target language
git clone https://github.com/go-delve/mcp-dap-server
cd mcp-dap-server
go build -o bin/mcp-dap-serverThe server uses stdio transport, allowing AI agents to spawn it on-demand. Configure your MCP client with the path to the binary.
This configuration works with Gemini CLI and similar MCP clients:
{
"mcpServers": {
"dap-debugger": {
"command": "mcp-dap-server",
"args": [],
"env": {}
}
}
}claude mcp add mcp-dap-server /path/to/mcp-dap-serverStart a debugging session. Supports three modes:
- source: Compile and debug Go source code
- binary: Debug a pre-compiled executable
- attach: Attach to a running process
Parameters:
mode(string, required): One of 'source', 'binary', or 'attach'path(string): Path to source file or binary (required for source/binary modes)args(array): Arguments to pass to the programprocessId(number): Process ID (required for attach mode)breakpoints(array): Breakpoints to set before running (file:line or function name)stopOnEntry(boolean): Stop at program entry pointport(number): DAP server port
Returns full context (location, stack trace, variables) when stopped.
End the debugging session. Terminates the debuggee and stops the debugger.
Restart the debugging session with optional new arguments.
- Parameters:
arguments(array, optional): New program arguments
Set a breakpoint at a file:line location or on a function.
- Parameters (one of):
file(string) +line(number): Source file and line numberfunction(string): Function name
Remove breakpoints from a file or clear all breakpoints.
- Parameters:
file(string, optional): Clear breakpoints in this fileall(boolean, optional): Clear all breakpoints
Continue program execution. Optionally run to a specific location.
- Parameters:
to(object, optional): Run-to-cursor target (file+line or function)
Returns full context when stopped.
Step through code execution.
- Parameters:
mode(string, required): One of 'over', 'in', or 'out'
Returns full context at new location.
Pause program execution.
- Parameters:
threadId(number): Thread ID to pause
Get full debugging context including current location, stack trace, and all variables.
- Parameters:
threadId(number, optional): Thread IDframeId(number, optional): Stack frame ID
Evaluate an expression in the current debugging context.
- Parameters:
expression(string): Expression to evaluateframeId(number, optional): Frame contextcontext(string, optional): Evaluation context ('watch', 'repl', 'hover')
Modify a variable's value in the debugged program.
- Parameters:
variablesReference(number): Variables reference from contextname(string): Variable namevalue(string): New value
Get program metadata.
- Parameters:
type(string, required): One of 'sources' or 'modules'
Disassemble code at a memory address.
- Parameters:
memoryReference(string): Memory addressinstructionOffset(number, optional): Offset from addressinstructionCount(number): Number of instructions to disassemble
Contributions are welcome! Please feel free to submit a Pull Request.
MIT
- Built with the Model Context Protocol SDK for Go
- Uses the Google DAP implementation for Go