Skip to main content
Glama
will-garrett

debugpy-mcp

by will-garrett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to debugpy-mcp

No user-submitted related servers found.

    Related Servers

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

    • mcp-dap

      ztripez
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that bridges MCP and the Debug Adapter Protocol, enabling AI coding agents to launch and control debug sessions, set breakpoints, step through code, and inspect variables.
      17
      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

    D1.9/5.0

    Scored across 8 tools

    Disambiguation3/5

    The tools have distinct names, but some overlap exists in functionality, such as debugpy_logs and debugpy_debugpy_logs, which could cause confusion. However, most tools like debugpy_attach and debugpy_breakpoint_plan target different aspects of debugging, helping to differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent pattern of prefixing with 'debugpy_' and using snake_case throughout, such as debugpy_attach and debugpy_breakpoint_plan. There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count5/5

    With 8 tools, this server is well-scoped for a debugging domain, providing a focused set without being overwhelming. Each tool appears to serve a specific purpose in debugging workflows, such as attaching, logging, and status checking, which is appropriate for the scope.

    Completeness3/5

    The tools cover key debugging operations like attaching, logging, and status, but there are notable gaps, such as missing tools for stepping through code, setting breakpoints dynamically, or handling variables. This could limit agents in performing comprehensive debugging tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources