# mcp-debugger

Headless step-through debugger over the Debug Adapter Protocol for coding agents. Sets breakpoints, steps through execution, and inspects variables without an IDE.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 179
- Author: debugmcp
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/debugmcp/mcp-debugger
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/mcp/mcp-debugger

## What it does

The server exposes Debug Adapter Protocol capabilities to AI agents through structured tools. It runs as a standalone Node.js process. That makes it suitable for Docker containers, CI pipelines, and cloud sandboxes without a desktop UI.

Under the hood, it drives native engines like Delve for Go, debugpy for Python, and CodeLLDB for compiled binaries. Agents can inspect memory or pause execution. Running Java debug targets requires an installed JDK.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add mcp-debugger -- npx -y @debugmcp/mcp-debugger
```

### Codex

**Platform CLI**
```bash
codex mcp add mcp-debugger -- npx -y @debugmcp/mcp-debugger
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "mcp-debugger": {
            "command": "npx",
            "args": [
                "-y",
                "@debugmcp/mcp-debugger"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "mcp-debugger": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@debugmcp/mcp-debugger"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add mcp-debugger npx -y @debugmcp/mcp-debugger
```

## When to use it
- step through failing application code line by line
- inspect variable values at breakpoints during execution
- attach to a running backend process inside a container
- evaluate expressions while a program is paused

## Example prompts
- Set a breakpoint at the start of handle_request in app.py and start debugging
- Attach to the running Go process using Delve and show the stack trace
- Step into the next function and print the local variables

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md