mcp-dap-server
A debugger MCP server: the agent sets breakpoints, steps through code and reads variables of a live program over DAP.
- 107 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The debugger launches programs, attaches to processes, evaluates code and alters variables, with no authorization.
Install
- Works in
Manual install
git clone https://github.com/go-delve/mcp-dap-serverFirst command of the Building from Source section; then `go build -o bin/mcp-dap-server`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The debugger launches programs, attaches to processes, evaluates code and alters variables, with no authorization.
This is third-party code. Review the repository files before installing.
What it does
The MCP server connects an agent to debuggers over the Debug Adapter Protocol. The agent launches a program from source, a binary or a core dump, or attaches to a running process, then sets breakpoints, steps, pauses and evaluates expressions. Every stop returns the full context: location, call stack and variables. The README lists 13 tools, including `debug`, `breakpoint`, `step`, `evaluate`, `set-variable` and `disassemble`. The transport is stdio, so the client spawns the server itself.
Who it is for. Go developers and engineers hunting a bug in a running program who want the agent to debug step by step instead of printing logs.
Good fit when
- An agent must find the cause of a crash and stop at the right line.
- You need the variable values that lead to the failure.
- Debugging runs on a core dump without launching the program.
- A service is already running and you attach to its PID.
Not a fit when
- The debugger cannot run next to production data and secrets.
- The server would be shared among several users.
- Reading a log or running tests is enough.
Example request
Start the program under the debugger, stop at the handler function and show the variable values on entry.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
MCP_DAP_LOG- Set to 1 to write a private log in the OS temp directory.
Limitations
Requires Go 1.24.4 or newer and a DAP-compatible debugger for the target language. It builds from source; the README describes no package-manager install. The debugger can launch programs, attach to processes, evaluate target code, see secrets and alter or terminate the debuggee. There is no authorization or multi-user mode; the server targets a single trusted client. When enabled, the log grows to 8 MiB and stays on disk, and GDB logs are not size-capped: treat them as sensitive data.
How to disable. Remove the server entry from the MCP client config and delete the binary. The log, if `MCP_DAP_LOG=1` was set, sits in the OS temp directory and is deleted by hand.
FAQ
Which launch modes does `debug` have?
Four: `source` compiles and debugs Go code, `binary` takes a built file, `core` reads a core dump, and `attach` connects to a process by PID.
What do step and continue return?
The full stop context: location, call stack and variables, so a separate state request is rarely needed.
Where are logs stored?
No log is written by default. `MCP_DAP_LOG=1` creates a private file in the OS temp directory, capped at 8 MiB.
Does it work beyond Go?
DAP is generic, but the README documents Go debugging through Delve and a `core` mode with GDB. Other languages need their own DAP debugger.
Can the server be exposed over the network?
No. It is a stdio server with no HTTP listener or authorization; Delve's internal socket binds to loopback only.
Discussion
No questions or reviews yet.
Related
MCP serversA debugger with no IDE: an agent sets breakpoints, steps through code and inspects variables in ten languages
The official Microsoft MCP server for debugging: a VS Code extension and a CLI give an agent breakpoints, steps, variables and expression evaluation
An MCP server for the Node.js debugger: breakpoints, stepping, variable inspection and expression evaluation at a pause
A command-line debugger for MCP servers from Giant Swarm: a REPL for tools, OAuth 2.1 and an MCP server mode for Cursor
MCP Server for WinDbg
MCP Server for WinDbg Crash Analysis
An MCP server that hands the agent the Windows debuggers: crash dump analysis, remote and kernel debugging in natural language
An MCP server that lets an agent read files, search code and run commands in a workspace
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| mcp-dap-server (this card) | no | not required | 107 | |
| DebugMCP | yes | not required | 581 | a VS Code multi-language debugger; mcp-dap-server is a standalone binary from the Delve team and handles core dumps |
| Node.js Debugger MCP | no | not required | 350 | debugs Node.js only; this one targets Go and any language with a DAP debugger |
README in short
The server runs over stdio and targets a single trusted client under a least-privileged OS account. The `skills/` folder holds instructions for source, binary, core dump and attach debugging.