gdb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gdb_sessionC | Start, stop, restart, or inspect the current GDB session. |
| gdb_loadC | Load a binary, core file, symbol file, and optional program arguments. |
| gdb_execC | Execute an arbitrary GDB CLI command with warning-and-confirm risk handling. |
| gdb_miC | Execute a raw GDB/MI command with warning-and-confirm risk handling. |
| gdb_remoteC | Configure or connect Windows GDB to a VM-side gdbserver. |
| gdb_contextB | Return registers, current instruction, disassembly, stack, backtrace, breakpoints, and mappings. |
| gdb_memoryC | Read, write, search, or dump inferior memory. |
| gdb_registerC | Read all registers, read one register, or write one register. |
| gdb_breakpointC | Add, delete, enable, disable, list, condition, or clear breakpoints/watchpoints. |
| gdb_run_controlC | Run, continue, step, next, instruction-step, finish, until, interrupt, kill, or restart. |
| gdb_analyzeC | Analyze crash state, registers, stack, exploitability, calling convention, or memory faults. |
| gdb_elfB | Inspect ELF metadata using pyelftools when available and readelf/objdump as fallback. |
| gdb_pwndbgC | Execute pwndbg/gef/peda helper commands if they appear available. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Tools mostly cover distinct GDB aspects (breakpoints, memory, registers, execution control, session), with minor overlap between 'gdb_context' and 'gdb_register' for register info, and 'gdb_exec' vs 'gdb_mi' for command execution.
All tools start with 'gdb_', but naming patterns vary: some are verbs (analyze, exec), some nouns (breakpoint, context), and one is verb_noun (run_control). No consistent verb_noun pattern.
13 tools is well-scoped for a GDB debugger server, covering essential operations without being overwhelming.
Covers most key GDB features (session, loading, breakpoints, execution, memory, registers, analysis, context, remote, plugins), though source-level debugging or variable inspection are missing but can be handled via gdb_exec.