MCP GDB Server
# MCP GDB Server
[](https://www.npmjs.com/package/mcp-gdb)
[](https://github.com/signal-slot/mcp-gdb/blob/main/LICENSE)
A Model Context Protocol (MCP) server that provides GDB debugging functionality for use with Claude or other AI assistants.
## Features
- 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
- View source code with VS Code integration
- Execute arbitrary GDB commands
## Installation
### Claude Code
```bash
claude mcp add gdb -- npx -y mcp-gdb
```
### Claude Desktop
Add the following to your Claude Desktop MCP configuration:
```json
{
"mcpServers": {
"gdb": {
"command": "npx",
"args": ["-y", "mcp-gdb"]
}
}
}
```
### Install from Source
```bash
git clone https://github.com/signal-slot/mcp-gdb.git
cd mcp-gdb
npm install
npm run build
```
## Usage
### Example Commands
Here are some examples of using the GDB MCP server through Claude:
#### Starting a GDB session
```
Use gdb_start to start a new debugging session
```
#### Loading a program
```
Use gdb_load to load /path/to/my/program with the sessionId that was returned from gdb_start
```
#### Setting a breakpoint
```
Use gdb_set_breakpoint to set a breakpoint at main in the active GDB session
```
#### Running the program
```
Use gdb_continue to start execution
```
#### Examining variables
```
Use gdb_print to evaluate the expression "my_variable" in the current context
```
#### Getting a backtrace
```
Use gdb_backtrace to see the current call stack
```
#### Terminating the session
```
Use gdb_terminate to end the debugging session
```
## Supported GDB Commands
- `gdb_start`: Start a new GDB session
- `gdb_load`: Load a program into GDB
- `gdb_command`: Execute an arbitrary GDB command
- `gdb_terminate`: Terminate a GDB session
- `gdb_list_sessions`: List all active GDB sessions
- `gdb_attach`: Attach to a running process
- `gdb_load_core`: Load a core dump file
- `gdb_set_breakpoint`: Set a breakpoint
- `gdb_continue`: Continue program execution
- `gdb_step`: Step program execution
- `gdb_next`: Step over function calls
- `gdb_finish`: Execute until the current function returns
- `gdb_backtrace`: Show call stack
- `gdb_print`: Print value of expression
- `gdb_examine`: Examine memory
- `gdb_info_registers`: Display registers
- `gdb_list_source`: List source code at current location or specified location with VS Code integration
## License
MIT
TDQS
Scored across 16 tools
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific GDB operation like attaching, stepping, examining memory, or managing sessions, making misselection unlikely.
All tools follow a consistent 'gdb_' prefix with descriptive verb_noun patterns (e.g., gdb_attach, gdb_backtrace, gdb_set_breakpoint). This predictability aids agent understanding and usage.
With 16 tools, the count is slightly high but reasonable for a GDB debugging server. It covers essential debugging operations without feeling overly heavy, though it could be streamlined slightly.
The toolset provides complete coverage for GDB debugging workflows, including session management, execution control, breakpoints, memory examination, and stack analysis. No obvious gaps exist for the domain.