MCP Catalogs
Home

mcp-dap-server

by go-delve·84·Score 48

MCP server that bridges AI assistants with DAP debuggers for programmatic debugging of live programs.

developer-toolsai-llmops-infra
13
Forks
3
Open issues
this month
Last commit
2d ago
Indexed

Overview

The MCP DAP Server provides a comprehensive interface between AI agents and debuggers through the Debug Adapter Protocol (DAP). It offers tools for session management, breakpoint control, execution flow management, and state inspection. The server handles multiple debugging modes including source code, binary, core dump analysis, and process attachment. With 13 well-documented tools, it enables AI systems to debug code in various programming languages with full programmatic control.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Automated debugging of applications by AI assistants
you:Remote debugging sessions controlled through AI agents
you:Programmatic analysis of application behavior and performance
you:What programming languages does this server support?
you:How does the server handle multiple debugging sessions?

When to choose this

Choose this server when you need AI agents to programmatically control debugging sessions across different programming languages with DAP-compatible debuggers.

When NOT to choose this

Don't choose this if you need debugging capabilities for languages without DAP support or if you require a graphical user interface for debugging.

Tools this server exposes

12 tools extracted from the README
  • debugmode, path, args, coreFilePath, processId, breakpoints, stopOnEntry, port

    Start a debugging session with various modes (source, binary, core, attach)

  • stop

    End the debugging session

  • restartarguments

    Restart the debugging session with optional new arguments

  • breakpointfile, line, function

    Set a breakpoint at a file:line location or on a function

  • clear-breakpointsfile, all

    Remove breakpoints from a file or clear all breakpoints

  • continueto

    Continue program execution, optionally run to a specific location

  • stepmode

    Step through code execution (over, in, or out)

  • pausethreadId

    Pause program execution on a specific thread

  • contextthreadId, frameId

    Get full debugging context including location, stack trace, and variables

  • evaluateexpression, frameId, context

    Evaluate an expression in the current debugging context

  • set-variablevariablesReference, name, value

    Modify a variable's value in the debugged program

  • disassemblememoryReference, instructionOffset, instructionCount

    Disassemble code at a memory address

Comparable tools

dap-go-mcpvscode-debug-server-mcpgdb-mcp-server

Installation

Installation

Prerequisites

  • Go 1.24.4 or later
  • A DAP-compatible debugger for your target language

Building from Source

git clone https://github.com/go-delve/mcp-dap-server
cd mcp-dap-server
go build -o bin/mcp-dap-server

MCP Client Configuration

Add to your MCP client configuration:

{
  "mcpServers": {
    "dap-debugger": {
      "command": "mcp-dap-server",
      "args": [],
      "env": {}
    }
  }
}

For Claude Code:

claude mcp add mcp-dap-server /path/to/mcp-dap-server

FAQ

What programming languages does this server support?
The MCP DAP Server works with any language that has a DAP-compatible debugger. It has been demonstrated with Go debugging through delve, but is designed to work with language-specific debuggers that support the Debug Adapter Protocol.
How does the server handle multiple debugging sessions?
Each debugging tool call creates a new session. The server manages multiple sessions separately, allowing debugging of different processes concurrently.

Compare mcp-dap-server with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.