Skip to main content
Glama
MCP GDB Server

MCP GDB Server

by signal-slot

MCP GDB Server

npm version 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

Related MCP server: GDB MCP Server

Installation

Claude Code

claude mcp add gdb -- npx -y mcp-gdb

Claude Desktop

Add the following to your Claude Desktop MCP configuration:

{
  "mcpServers": {
    "gdb": {
      "command": "npx",
      "args": ["-y", "mcp-gdb"]
    }
  }
}

Install from Source

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

Available Tools

16 tools
gdb_attachC

Attach to a running process

Inputs: pid (required), sessionId (required).

gdb_backtraceC

Show call stack

Inputs: sessionId (required), full, limit.

gdb_commandC

Execute a GDB command

Inputs: command (required), sessionId (required).

gdb_continueC

Continue program execution

Inputs: sessionId (required).

gdb_examineC

Examine memory

Inputs: expression (required), sessionId (required), count, format.

gdb_finishC

Execute until the current function returns

Inputs: sessionId (required).

gdb_info_registersC

Display registers

Inputs: sessionId (required), register.

gdb_list_sessionsB

List all active GDB sessions

Inputs: no named parameters.

gdb_loadC

Load a program into GDB

Inputs: program (required), sessionId (required), arguments.

gdb_load_coreC

Load a core dump file

Inputs: corePath (required), program (required), sessionId (required).

gdb_nextC

Step over function calls

Inputs: sessionId (required), instructions.

gdb_printC

Print value of expression

Inputs: expression (required), sessionId (required).

gdb_set_breakpointC

Set a breakpoint

Inputs: location (required), sessionId (required), condition.

gdb_startC

Start a new GDB session

Inputs: gdbPath, workingDir.

gdb_stepC

Step program execution

Inputs: sessionId (required), instructions.

gdb_terminateC

Terminate a GDB session

Inputs: sessionId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 16 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides structured debugging capabilities through LLDB, enabling AI assistants to set breakpoints, inspect variables, analyze crashes, disassemble code, and evaluate expressions in C/C++ programs.
      17
      3
      Apache 2.0
    • A
      license
      C
      quality
      B
      maintenance
      Enables LLM clients to interact with the GNU Debugger (GDB) for comprehensive debugging and binary analysis. It provides a wide range of tools for program execution control, memory examination, stack analysis, and disassembly.
      13
      74
      GPL 3.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to start and manage LLDB debugging sessions, including loading programs, setting breakpoints, stepping through code, and examining memory.
      19
      1
      MIT