MCP GDB 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gdb_startC | Start a new GDB session |
| gdb_loadC | Load a program into GDB |
| gdb_commandC | Execute a GDB command |
| gdb_terminateC | Terminate a GDB session |
| gdb_list_sessionsB | List all active GDB sessions |
| gdb_attachC | Attach to a running process |
| gdb_load_coreC | Load a core dump file |
| gdb_set_breakpointC | Set a breakpoint |
| gdb_continueC | Continue program execution |
| gdb_stepC | Step program execution |
| gdb_nextC | Step over function calls |
| gdb_finishC | Execute until the current function returns |
| gdb_backtraceC | Show call stack |
| gdb_printC | Print value of expression |
| gdb_examineC | Examine memory |
| gdb_info_registersC | Display registers |
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 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.