dap-mcp

Created By
KashunChenga year ago
Model Context Protocol (MCP) server that interacts with a Debugger
Overview

What is dap-mcp?

The dap-mcp is an implementation of the Model Context Protocol (MCP) designed to manage Debug Adapter Protocol (DAP) sessions, optimizing the context window of large language models to enhance debugging workflows.

How to use dap-mcp?

To use dap-mcp, install it via pip and run the server with a JSON configuration file specifying debugger settings and source directories. Example command: pip install dap-mcp followed by python -m dap_mcp --config config.json.

Key features of dap-mcp?

  • Integration with Debug Adapter Protocol for standardized debugging.
  • Utilization of MCP to optimize context for debugging.
  • Tools for setting, listing, and removing breakpoints, controlling execution, evaluating expressions, and viewing source code.
  • Customizable settings through a JSON configuration file.

Use cases of dap-mcp?

  1. Streamlining debugging processes in software development.
  2. Enhancing the debugging experience for large language models.
  3. Facilitating the integration of various DAP servers through configuration.

FAQ from dap-mcp?

  • What programming languages does dap-mcp support?

dap-mcp is primarily designed for Python debugging but can be extended to support other languages through additional configurations.

  • Is dap-mcp open source?

Yes, dap-mcp is open source and contributions are welcome.

  • How can I contribute to dap-mcp?

You can contribute by forking the repository, creating a new branch, writing tests, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
KashunCheng
Star
2
Language
Python
License
AGPL-3.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago