GDB Lite 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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gdb_spawnA | Start a gdb session and return a session id. Supports local programs, core files, attach, remote targets, and extra native gdb args. |
| gdb_execB | Send a gdb command and return all output since the previous gdb_exec or gdb_interrupt call. Empty command only polls output. |
| gdb_interruptB | Send SIGINT to the gdb session/debuggee, wait for the GDB prompt, and return incremental output. |
| gdb_closeC | Terminate and remove a gdb session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| debug-guide | Fallback workflow guide for LLM agents using GDB Lite MCP without a dedicated Skill. |
TDQS
Scored across 4 tools
Each tool has a distinct role: spawning, executing commands, interrupting, and closing sessions. There is no overlap or ambiguity between them.
All tools follow a consistent 'gdb_' prefix with a clear verb (spawn, exec, interrupt, close), making the naming pattern predictable and understandable.
With only 4 tools, the set is minimal but covers the core operations for managing a GDB session. It could benefit from additional tools like session listing, but is reasonable for a 'lite' implementation.
The tools cover the essential lifecycle of a GDB session: start, execute commands, send interrupts, and close. Minor gaps like session listing are acceptable for a lite MCP.