Cette page est affichée en anglais. Une traduction française est en cours.
MCP ConfigsMay 11, 2026·2 min de lecture

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
MCP Hub · Community
Prêt pour agents

Cet actif peut être lu et installé directement par les agents

TokRepo expose une commande CLI universelle, un contrat d'installation, le metadata JSON, un plan selon l'adaptateur et le contenu raw pour aider les agents à juger l'adaptation, le risque et les prochaines actions.

Stage only · 17/100Stage only
Surface agent
Tout agent MCP/CLI
Type
Mcp Config
Installation
Stage only
Confiance
Confiance : Established
Point d'entrée
Asset
Commande CLI universelle
npx tokrepo install 5577aacb-0724-477d-b639-70ffa3cdba9d
contrat d'installationJSON metadataplan adaptateurcontenu raw
Introduction

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 et remerciements

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

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires

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
◈Accueil🔍Rechercher👤Moi