Is mcp-debugger — DAP Debugging Tools for Agents free to use?

Yes. mcp-debugger — DAP Debugging Tools for Agents is freely available on TokRepo. Check the Source & Thanks section on the asset page for the specific open-source license.

How do I install mcp-debugger — DAP Debugging Tools for Agents?

Visit the asset page on TokRepo and click "Copy for agent" to get the installation instructions. Most assets can be installed with a single command.

MCP ConfigsMay 11, 2026·2 min read

mcp-debugger — DAP Debugging Tools for Agents

Add step-through debugging to AI agents via an MCP server built on the Debug Adapter Protocol (DAP). Works across languages; run with npm or Docker.

MCP Hub · Community

Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage

Agent surface

Any MCP/CLI agent

Kind

Mcp Config

Install

Stage only

Trust

Trust: Established

Entrypoint

Asset

Safe staging command

npx -y tokrepo@latest install 5577aacb-0724-477d-b639-70ffa3cdba9d --target codex

Stages files first; activation requires review of the staged README and plan.

Intro

Add step-through debugging to AI agents via an MCP server built on the Debug Adapter Protocol (DAP). Works across languages; run with npm or Docker.

Best for: AI coding agents that need deterministic debugging actions (breakpoints, stepping, stack/vars) instead of log guessing
Works with: MCP clients + DAP-based debuggers; multi-language projects (see repo for adapters)
Setup time: 10 minutes

How to Use It Well

Setup time ~10 minutes (npm + connect from your MCP client)
GitHub stars + forks (verified): see Source & Thanks
One MCP tool call can replace multiple “please step/print/inspect” prompt turns

If your agent’s debugging loop is “edit → run → read logs → guess”, you waste tokens and time. With mcp-debugger, you can make debugging state explicit: set one breakpoint, step a few frames, and inspect locals/stack via structured calls.

FAQ

Q: What does it actually expose? A: A set of MCP tools that map to DAP-style debugging actions like create session, breakpoints, stepping, stack and variables.

Q: Do I need an IDE UI? A: No. Agents can drive debugging headlessly by calling MCP tools; your IDE is optional.

Q: Is it safe for production? A: Use it in dev/CI environments. Limit what files/processes the debugger can touch and run it with least privilege.

🙏

Source & Thanks

Source: https://github.com/debugmcp/mcp-debugger > License: MIT > GitHub stars: 105 · forks: 15

Discussion

No comments yet. Be the first to share your thoughts.

Related Assets

Chrome DevTools MCP — Browser Debugging for AI Agents

Give your AI coding agent full access to Chrome DevTools for browser automation, debugging, and performance analysis. Works with Claude, Cursor, Copilot, and 15+ AI tools.

MCP Configs

MCP Hub

Apify MCP Server — 8,000+ Web Scrapers for Agents

Apify MCP Server connects agents to Apify Actors via a hosted endpoint (mcp.apify.com) or local run, turning thousands of web scrapers into callable tools.

MCP Configs

MCP Hub

Google Workspace MCP — Gmail Drive Calendar for AI

Official Google CLI with built-in MCP server for all Workspace APIs. One command gives AI agents access to Gmail, Drive, Calendar, Docs, Sheets, and 10+ Google services.

MCP Configs

MCP Hub

omega-memory — Persistent Memory for Coding Agents

OMEGA is a local-first, cross-model memory system for coding agents. It runs an MCP server plus hooks so recall is automatic across sessions.

MCP Configs

MCP Hub

◈Home 🔍Search 👤Me