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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago