Skip to main content
Glama
Micro-Evaluation-Group

pwndbg-lldb-mcp

by Micro-Evaluation-Group
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pwndbg-lldb-mcp

No user-submitted related servers found.

    Related Servers

    • RE-MCP Server

      Steeve-Crypto
      A
      license
      Not graded
      quality
      D
      maintenance
      A local, privacy-first MCP server that orchestrates Ghidra, Binary Ninja, x64dbg, and system tools to provide AI assistants with powerful binary analysis capabilities.
      Academic Free v1.1

    • re-mcp

      jtsylve
      A
      license
      A
      quality
      C
      maintenance
      A multi-backend MCP server that exposes binary analysis capabilities from IDA Pro and Ghidra, allowing LLMs to directly drive reverse-engineering tools via natural language.
      11
      166
      Apache 2.0

    • gdb-mcp

      datobena
      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
      1,587 PyPI
      3
      MIT

    • gdb_mcp

      airfloats
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to control GDB debugging sessions, including breakpoint management, thread analysis, and variable inspection, using the GDB/MI protocol.
      22
      1
      MIT

    • gdb and rr Debugging

      schuay
      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
    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

    C2.8/5.0

    Scored across 153 tools

    Disambiguation2/5

    Many tools have overlapping purposes (e.g., multiple bin types: fastbins, smallbins, largebins, unsortedbin, tcachebins, plus generic bins). Also, numerous stepping/next commands (nextcall, nextjmp, nextret, etc.) have subtle distinctions that are hard to differentiate. An agent would frequently misselect.

    Naming Consistency4/5

    All tools follow a consistent 'pwndbg_' prefix with lowercase and underscores, matching the original pwndbg command names. However, there is no verb-noun pattern; most are simple nouns (e.g., pwndbg_heap, pwndbg_arena). This is acceptable but slightly less predictable.

    Tool Count1/5

    153 tools is excessive for an MCP server. While pwndbg is feature-rich, exposing every command as a separate tool overwhelms agents. Many tools are niche (e.g., pwndbg_tips, pwndbg_bugreport) and could be combined or omitted. A typical debugger server should have 10-30 tools.

    Completeness3/5

    The tool set covers most pwndbg features, including heap analysis, kernel debugging, memory inspection, and stepping. However, some fundamental debugger operations are missing (e.g., direct register write beyond flags, or a generic memory write tool). There are also redundant equivalents (e.g., both LLDB native and pwndbg versions of thread listing).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources