gdb and rr Debugging
Related Servers
Alternatives to gdb and rr Debugging
- AlicenseBqualityCmaintenanceProvides 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.1635 npm159MIT
- AlicenseNot gradedqualityBmaintenanceA GDB/MI protocol server based on the MCP protocol, providing remote application debugging capabilities.68MIT
- AlicenseCqualityDmaintenanceEnables 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.1372GPL 3.0
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to control GDB debugging sessions, including breakpoint management, thread analysis, and variable inspection, using the GDB/MI protocol.221MIT
- AlicenseBqualityCmaintenanceMCP server that wraps gdb to enable LLMs to drive live debugging sessions, including starting sessions on binaries, attaching to processes, and running commands.72,593 PyPI3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes LLDB debugging capabilities, enabling AI-assisted interactive debugging of C/C++ applications through 40 specialized tools.4MIT
- AlicenseBqualityDmaintenanceA 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.410 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with GDB for debugging via the MCP protocol. Supports setting breakpoints, stepping through code, inspecting memory and registers, and more.85MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides programmatic access to the GNU Debugger (GDB), enabling AI models to interact with GDB through natural language for debugging tasks.9Apache 2.0
TDQS
Scored across 34 tools
Each tool has a distinct purpose clearly described. For example, step and next are separated by whether they enter function calls, and reverse tools are clearly prefixed. There is minimal overlap; batch_commands and exec_command serve different needs (sequential vs. single command).
All tools use consistent snake_case verb_noun or verb phrase patterns. Reverse tools follow a uniform 'reverse-verb' naming. No mixed conventions like camelCase or inconsistent verb styles.
34 tools is on the high end but appropriate for the comprehensive domain of GDB and rr debugging. Each tool covers a specific aspect without redundancy. The count feels slightly heavy but earns a high score due to the scope of the server.
The tool set covers all major debugging workflows: session management, breakpoints, stepping (forward/reverse, source/instruction), stack navigation, memory inspection, registers, source listing, variables, watchpoints, and escape hatch. rr tools include recording, replay, and all reverse stepping variants, leaving no obvious gaps.