Skip to main content
Glama

Related Servers

Alternatives to gdb_mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides programmatic access to the GNU Debugger (GDB), enabling AI models to interact with GDB through natural language for debugging tasks.
      9
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes GDB debugging as tools. An AI assistant can set breakpoints, run programs, step through code, inspect variables and memory, and examine registers — all via structured tool calls. Reverse debugging with rr is also supported.
      34
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes LLDB debugging capabilities, enabling AI-assisted interactive debugging of C/C++ applications through 40 specialized tools.
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A lightweight MCP server that enables LLM agents to interact with GDB for debugging native programs, supporting spawning sessions, executing commands, interrupting hangs, and closing sessions.
      4
      10 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      MCP server that wraps gdb to enable LLMs to drive live debugging sessions, including starting sessions on binaries, attaching to processes, and running commands.
      7
      2,593 PyPI
      3
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to control GDB debugger via MCP protocol for local and remote debugging, supporting CTF Pwn, crash analysis, and ELF inspection.
      13
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool has a distinct purpose: session management, breakpoint operations, execution control, state inspection, and selection. There is no overlap; even stepping and continuing are clearly differentiated.

    Naming Consistency5/5

    All tool names follow the consistent pattern gdb_<verb> or gdb_<verb>_<noun> (e.g., gdb_set_breakpoint, gdb_get_backtrace). The prefix and naming style are uniform.

    Tool Count5/5

    22 tools cover the essential GDB debugging workflow without being excessive. Each tool serves a necessary function, and the count is well-scoped for a debugger server.

    Completeness5/5

    The tool surface covers the full debugging lifecycle: session start/stop, breakpoint management, execution control, thread/stack inspection, variable/register access, and expression evaluation. Any missing features can be accessed via gdb_execute_command, making the set comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues