Skip to main content
Glama
zjm1060

GDB MCP Server

by zjm1060
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to GDB MCP Server

No user-submitted related servers found.

    Related Servers

    • GDB MCP Server

      yywz1999
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with GDB for debugging via the MCP protocol. Supports setting breakpoints, stepping through code, inspecting memory and registers, and more.
      85
      MIT

    • GDB MCP Server

      smadi0x86
      A
      license
      C
      quality
      D
      maintenance
      Enables LLM clients to interact with the GNU Debugger (GDB) for comprehensive debugging and binary analysis. It provides a wide range of tools for program execution control, memory examination, stack analysis, and disassembly.
      13
      72
      GPL 3.0
    • sbl-debugger by soundbytelabs

      sbl-debuggerofficial

      soundbytelabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to debug ARM Cortex-M targets via GDB and OpenOCD, supporting attach, breakpoints, stepping, register/memory inspection, and SVD peripheral decoding.
      MIT

    • embedded-gdb-mcp

      vividcode-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables GDB debugging for embedded development workflows, allowing users to start sessions, load programs, set breakpoints, step through code, and examine memory/registers/variables via natural language.
      3
      MIT

    • gdb-mcp

      traver88
      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
    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 31 tools

    Disambiguation4/5

    Most tools have clear distinct purposes, but some overlap exists between gdb_run/gdb_continue and gdb_next/gdb_step. The descriptions help differentiate, but an agent might still confuse similar actions.

    Naming Consistency5/5

    All tools follow a consistent 'gdb_verb_noun' pattern in snake_case, making the naming predictable and easy to interpret for both agents and humans.

    Tool Count2/5

    31 tools is high for typical MCP server coherence; while GDB debugging is complex, the count exceeds the 25-tool threshold for 'too many' and could be streamlined (e.g., combining some list operations).

    Completeness4/5

    The tool set covers most core GDB workflows (breakpoints, stepping, memory, registers, expressions, threads). Minor gaps like watchpoints or variable modification exist, but overall it's comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources