Skip to main content
Glama
benpm

LLDB MCP Server

by benpm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to LLDB MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • lldb-mcp

      ant4g0nist
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with LLDB debugging sessions through a standardized MCP interface, allowing natural language commands for debugging tasks like setting breakpoints, stepping, and evaluating expressions.
      757
      Apache 2.0

    • cpp-debug-mcp

      William-An
      A
      license
      A
      quality
      C
      maintenance
      Provides GDB and clangd-based tools for debugging C++ programs, enabling step execution, variable inspection, diagnostics, and combined runtime-static analysis.
      27
      1
      MIT

    • MCP GDB Server

      signal-slot
      A
      license
      B
      quality
      C
      maintenance
      Provides GDB debugging functionality for use with Claude or other AI assistants, allowing users to manage debugging sessions, set breakpoints, examine variables, and execute GDB commands through natural language.
      16
      35 npm
      159
      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

    A4.2/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific debugger operations, such as analyzing crashes, viewing backtraces, disassembling code, evaluating expressions, examining variables, listing images, reading memory, viewing registers, running programs, executing commands, setting breakpoints, showing source, looking up symbols, listing threads, checking version, and setting watchpoints. No tools appear to overlap in functionality, making it easy for an agent to select the correct one.

    Naming Consistency5/5

    All tool names follow a consistent 'lldb_' prefix with a descriptive verb_noun pattern, such as lldb_analyze_crash, lldb_backtrace, lldb_disassemble, etc. This uniformity enhances readability and predictability, allowing agents to easily understand and navigate the toolset without confusion from mixed naming conventions.

    Tool Count5/5

    With 17 tools, the server is well-scoped for a comprehensive debugger interface, covering essential operations like execution control, inspection, and analysis. Each tool serves a specific and necessary function in the debugging workflow, avoiding redundancy while ensuring complete coverage of typical debugging tasks.

    Completeness5/5

    The toolset provides complete coverage of the LLDB debugging domain, including core operations like running programs, setting breakpoints and watchpoints, examining state (variables, registers, memory), analyzing crashes, and accessing symbols and source code. No significant gaps are evident; agents can perform full debugging workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources