gdb_mcp
Related Servers
Alternatives to gdb_mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityCmaintenanceMCP 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.343MIT
- 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
- 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
- AlicenseBqualityDmaintenanceEnables AI assistants to control GDB debugger via MCP protocol for local and remote debugging, supporting CTF Pwn, crash analysis, and ELF inspection.131MIT
TDQS
Scored across 22 tools
Each tool has a distinct purpose: session management, breakpoint operations, execution control, state inspection, and selection. There is no overlap; even stepping and continuing are clearly differentiated.
All tool names follow the consistent pattern gdb_<verb> or gdb_<verb>_<noun> (e.g., gdb_set_breakpoint, gdb_get_backtrace). The prefix and naming style are uniform.
22 tools cover the essential GDB debugging workflow without being excessive. Each tool serves a necessary function, and the count is well-scoped for a debugger server.
The tool surface covers the full debugging lifecycle: session start/stop, breakpoint management, execution control, thread/stack inspection, variable/register access, and expression evaluation. Any missing features can be accessed via gdb_execute_command, making the set comprehensive.