Skip to main content
Glama
FlyDut

debug-dap-mcp

by FlyDut
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to debug-dap-mcp

No user-submitted related servers found.

    Related Servers

    • qwen-dap-mcp

      SLP-DEV1
      A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to connect to Debug Adapter Protocol debuggers over MCP, allowing them to launch or attach to native targets, control execution, set breakpoints and watchpoints, inspect stacks, variables, memory, and exceptions, and capture agent-friendly debugger snapshots.
      14
      104 npm
      2
      Apache 2.0

    • hostproto-dap-debugpy

      bayleafwalker
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables launching and controlling a debugpy debug session through MCP, including setting breakpoints, stepping, evaluating expressions, and observing debugger state and events.
      MIT

    • oh-mcp-dap

      phimage
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides a real debugger via the Debug Adapter Protocol, exposing a single 'debug' tool to launch/attach, control execution, and inspect program state across gdb, lldb, debugpy, and more.
      -

    • Watchtower DAP Windows

      rlaksana
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables step-through debugging for C#, Node.js/TypeScript, Python, and Dart applications on Windows through a unified MCP interface. Acts as a bridge between MCP clients and various debug adapters, providing consistent debugging workflows with breakpoints, variable inspection, and process attachment capabilities.
      7 npm
      ISC

    • Debug-MCP

      Kaina3
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform interactive Python debugging with breakpoints, step execution, and variable inspection using the Debug Adapter Protocol (DAP) through an MCP server interface.
      8
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so no ambiguity exists between tools. The 31 DAP actions are internal parameters, not separate tools.

    Naming Consistency5/5

    The single tool name `debug` is concise and matches the server's purpose. With only one tool, there is no conflicting naming pattern.

    Tool Count2/5

    The entire DAP protocol is packed into one mult-i purpose dispatch tool, which feels too few for the apparent scope. A single optool acts as a god-parameter surface rather than a discoverable set.

    Completeness5/5

    The 31 actions likely cover the core DAP request lifecycle (launch, attach, breakpoints, stepping, evaluation, etc.), enabling complete debugging workflows. As a single control surface, there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources