Skip to main content
Glama
iarmankhan

agentic-debugger

by iarmankhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to agentic-debugger

No user-submitted related servers found.

    Related Servers

    • 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

    • Super Debugger

      ahernandezvega907-crypto
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets AI agents debug Python code by running scripts, setting breakpoints, stepping through execution, inspecting live variable values, and editing or reverting files to verify fixes. It relies only on Python's standard sys.settrace, requiring no debugpy, DAP, pdb, or PTY.
      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.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: adding, listing, and removing instruments; starting and stopping debug sessions; and reading and clearing logs. The descriptions make it easy to differentiate between them, such as distinguishing 'add_instrument' from 'remove_instruments' and 'read_debug_logs' from 'clear_debug_logs'.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as 'add_instrument', 'clear_debug_logs', and 'start_debug_session'. There are no deviations in naming conventions, making the set predictable and easy to understand.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a debugger server, covering core operations like instrument management, session control, and log handling. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness5/5

    The tool set provides complete coverage for a debugger's lifecycle: it includes CRUD operations for instruments (add, list, remove), session management (start, stop), and log handling (read, clear). There are no obvious gaps, as all essential workflows are supported without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources