A Model Context Protocol (MCP) server that provides GDB debugging functionality for use with Claude or other AI assistants.
- Start and manage GDB debugging sessions
- Load programs and core dumps for analysis
- Set breakpoints, step through code, and examine memory
- View call stacks, variables, and registers
- Execute arbitrary GDB commands
# Clone the repository
git clone https://github.com/signal-slot/mcp-gdb.git
cd mcp-gdb
# Install dependencies
npm install
# Build the project
npm run build
- Configure the MCP settings in the Claude desktop app or browser extension to include this server:
{
"mcpServers": {
"gdb": {
"command": "node",
"args": ["/path/to/mcp-gdb/build/index.js"],
"disabled": false
}
}
}
-
Restart Claude or refresh the page.
-
Now you can use the GDB tools in your conversations with Claude.
Here are some examples of using the GDB MCP server through Claude:
Use gdb_start to start a new debugging session
Use gdb_load to load /path/to/my/program with the sessionId that was returned from gdb_start
Use gdb_set_breakpoint to set a breakpoint at main in the active GDB session
Use gdb_continue to start execution
Use gdb_print to evaluate the expression "my_variable" in the current context
Use gdb_backtrace to see the current call stack
Use gdb_terminate to end the debugging session
gdb_start
: Start a new GDB sessiongdb_load
: Load a program into GDBgdb_command
: Execute an arbitrary GDB commandgdb_terminate
: Terminate a GDB sessiongdb_list_sessions
: List all active GDB sessionsgdb_attach
: Attach to a running processgdb_load_core
: Load a core dump filegdb_set_breakpoint
: Set a breakpointgdb_continue
: Continue program executiongdb_step
: Step program executiongdb_next
: Step over function callsgdb_finish
: Execute until the current function returnsgdb_backtrace
: Show call stackgdb_print
: Print value of expressiongdb_examine
: Examine memorygdb_info_registers
: Display registers
MIT