Skip to main content
Glama
ztripez

mcp-dap

by ztripez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-dap

No user-submitted related servers found.

    Related Servers

    • dap-mcp

      KashunCheng
      A
      license
      Not graded
      quality
      C
      maintenance
      An implementation of the Model Context Protocol (MCP) that enables interaction with debug adapters, allowing language models to control debuggers, set breakpoints, evaluate expressions, and navigate source code during debugging sessions.
      40
      AGPL 3.0

    • 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

    • VSCode Debug MCP

      PeakBI
      F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server and VS Code extension that enables AI clients to interactively debug code using breakpoints, execution control, and state inspection. It is language-agnostic and works with any debugger that supports VS Code's launch.json configurations.
      -

    • DebugPilot

      inkan-tech
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect debug state, control execution, and set breakpoints in VS Code by exposing the Debug Adapter Protocol as an MCP server.
      Apache 2.0
    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.5/5.0

    Scored across 17 tools

    Disambiguation4/5

    Each tool maps to a distinct debugger action: session lifecycle, breakpoint control, stepping, and inspection. The only mild ambiguity is between debug_get_pending_events (which includes output events) and debug_get_output (raw stdout/stderr), but the descriptions mostly clarify the separation.

    Naming Consistency5/5

    All tools use the same debug_ prefix followed by a clear verb_noun pattern (e.g., debug_set_breakpoints, debug_step_over, debug_get_threads). The naming is highly predictable and makes the purpose of each tool easy to infer.

    Tool Count4/5

    17 tools is slightly above the typical well-scoped range, but each tool corresponds to a necessary DAP operation. The set is not bloated; it covers a reasonable breadth of debugging functionality without obvious redundancy.

    Completeness4/5

    The set covers session launch/attach/disconnect, breakpoint management, execution control, stack/scope/variable inspection, evaluation, and output retrieval. Minor gaps exist, such as listing existing breakpoints or setting variable values, but core debugging workflows are adequately supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources