Skip to main content
Glama
MikeWinkelmannXL2

python-dap-mcp

by MikeWinkelmannXL2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to python-dap-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • 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

    • 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

    • debugpy-mcp

      will-garrett
      F
      license
      D
      quality
      D
      maintenance
      An MCP server that enables agents to attach debugpy to running Python processes inside Docker containers for enhanced debugging and inspection. It provides tools for container autodiscovery, process injection, and generating breakpoint plans based on logs and metadata.
      8
      -
    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

    A4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly distinct, but evaluate_expression and get_variable_details both operate on the top stack frame and could be confused (expression vs. variable name). The step commands are well differentiated, and the rest of the tools have unambiguous purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun or verb_adverb pattern (launch, set, clear, step, get, evaluate, end, continue). The naming is predictable and intuitive, with no mixed conventions.

    Tool Count5/5

    11 tools is well-scoped for a debugger server. Each tool serves a clear, essential purpose in the debugging workflow without redundancy or bloat.

    Completeness4/5

    The tool set covers the core debugger lifecycle: launch, breakpoints, stepping, stack inspection, expression evaluation, and termination. Minor gaps exist (e.g., listing all variables, exception breakpoints) but are not critical for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources