GDB MCP Server
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 |
|---|---|
| debugger_statusB | Get status of available debuggers. |
| debugger_startC | Start a debugging session with auto-detection or specified debugger type. |
| debugger_terminateB | Terminate a debugging session. |
| debugger_list_sessionsB | List all active debugging sessions. |
| debugger_commandC | Execute an arbitrary debugger command. |
| gdb_startC | Start a new GDB debugging session. |
| gdb_terminateB | Terminate a GDB debugging session. |
| gdb_list_sessionsB | List all active GDB sessions. |
| gdb_commandC | Execute any arbitrary GDB command. Use this for all GDB operations. |
| lldb_startB | Start a new LLDB debugging session. |
| lldb_terminateB | Terminate an LLDB debugging session. |
| lldb_list_sessionsB | List all active LLDB sessions. |
| lldb_commandC | Execute an arbitrary LLDB command. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_gdb_sessions | Resource that provides information about active GDB sessions. |
TDQS
Scored across 13 tools
There is significant ambiguity between the generic debugger_* tools and the specific gdb_* and lldb_* tools. For example, debugger_start and gdb_start/lldb_start appear to serve overlapping purposes, and the descriptions don't clarify when to use which. This creates confusion about tool selection boundaries.
All tool names follow a consistent verb_noun pattern with snake_case throughout. The naming is predictable and organized, with clear prefixes (debugger_, gdb_, lldb_) for different tool groups.
13 tools is a reasonable count for a debugger server, but it feels borderline due to redundancy. The duplication between generic and specific tools makes the set feel heavier than necessary, suggesting the count could be optimized.
The tool set covers essential debugger operations: starting, listing, terminating sessions, and executing commands for both GDB and LLDB. Minor gaps might include session-specific status queries or more granular control, but core debugging workflows are well-supported.