Skip to main content
Glama
Kaina3

Debug-MCP

by Kaina3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Debug-MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • vibe-debug

      illscience
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables coding agents to use a real debugger (Python via debugpy) for launching, attaching, setting breakpoints, stepping through code, inspecting stack frames, and evaluating expressions through MCP tools.
      27
      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

    • VSCode Debug MCP

      primax79
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes VS Code's Debug Adapter Protocol as MCP tools, enabling AI coding agents to set breakpoints, step through code, inspect variables, and read exceptions in a real debug session.
      GPL 3.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.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose within the debug session lifecycle: create, end, state, breakpoint, continue, and three distinct step types. The descriptions specify unique actions like 'step into' vs 'step over', eliminating any ambiguity between tools.

    Naming Consistency5/5

    All tools follow a perfect 'sessions_verb' pattern (e.g., sessions_create, sessions_step_over). This consistent naming convention makes the tool set predictable and easy to understand at a glance.

    Tool Count5/5

    With 8 tools, this server provides a well-scoped set for debugging operations. It covers the essential debug session lifecycle (create, state, end) and core execution control (breakpoint, continue, step variations) without being overwhelming or sparse.

    Completeness5/5

    The tool set offers complete coverage for a debug session domain: creation, state monitoring, execution control (breakpoint, continue, step in/out/over), and cleanup. There are no obvious gaps; agents can fully manage debug sessions from start to finish.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources