Skip to main content
Glama
signal-slot

MCP GDB Server

by signal-slot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP GDB Server

No user-submitted related servers found.

    Related Servers

    • 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

    • MCP LLDB Server

      ankur106
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to start and manage LLDB debugging sessions, including loading programs, setting breakpoints, stepping through code, and examining memory.
      19
      1
      MIT

    • LLDB MCP Server

      benpm
      A
      license
      A
      quality
      D
      maintenance
      Provides structured debugging capabilities through LLDB, enabling AI assistants to set breakpoints, inspect variables, analyze crashes, disassemble code, and evaluate expressions in C/C++ programs.
      17
      3
      Apache 2.0

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

    B3.3/5.0

    Scored across 16 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific GDB operation like attaching, stepping, examining memory, or managing sessions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent 'gdb_' prefix with descriptive verb_noun patterns (e.g., gdb_attach, gdb_backtrace, gdb_set_breakpoint). This predictability aids agent understanding and usage.

    Tool Count4/5

    With 16 tools, the count is slightly high but reasonable for a GDB debugging server. It covers essential debugging operations without feeling overly heavy, though it could be streamlined slightly.

    Completeness5/5

    The toolset provides complete coverage for GDB debugging workflows, including session management, execution control, breakpoints, memory examination, and stack analysis. No obvious gaps exist for the domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources