Skip to main content
Glama
523,259 tools. Updated 2026-09-06 13:32

"Debugging software using GDB (GNU Debugger)" matching MCP tools:

  • Remove a debugger breakpoint by its ID to resume normal execution flow, cleaning up active breakpoints in Chrome debugging sessions.
    MIT
  • Skip function calls to execute the current line and pause at the next line while debugging. Requires an active paused debugger session. Use to avoid stepping into internals.
    MIT
  • Open a recorded core/minidump with a local debugger adapter and capture bounded postmortem evidence (stack, locals, registers, modules, disassembly) without executing the crashed program.
    Apache 2.0
  • Start a GDB debugging session for executable, core dump, or custom commands. Detects missing debug symbols and other warnings, returning a session ID for further debugging tools.
    MIT
  • Check service availability and retrieve version details for the GNU units converter, including database source and data version.
    GPL 3.0

Matching MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    MCP server that exposes GDB debugging as tools. An AI assistant can set breakpoints, run programs, step through code, inspect variables and memory, and examine registers — all via structured tool calls. Reverse debugging with rr is also supported.
    34
    3
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that provides programmatic access to the GNU Debugger (GDB), enabling AI models to interact with GDB through natural language for debugging tasks.
    9
    Apache 2.0

Matching MCP Connectors

  • Agent Replay Debugger MCP — record every agent step + deterministic replay. Step-debugger for

  • HexisOAuth

    Git-backed platform for skills, tools, and context for AI agents

  • Inspect stopped debugger sessions or core dumps and launch DAP debuggers to gather stack, variables, and exception evidence, returning a root-cause diagnosis with verification status.
    Apache 2.0
    Destructive
  • Step backward through program execution to undo instructions and examine previous states. Requires active GDB recording for reverse debugging.
    MIT
  • Load an ELF file into GDB for source-level debugging with symbols. Set flash=true to additionally program the firmware onto the target.
    MIT
  • Disconnect the GDB client from the debugging session while leaving the GDB server active for future connections.
    MIT
  • Stop active debug sessions and terminate OpenOCD/GDB processes to end embedded system debugging operations.
    MIT
  • Check GDB version and verify if GEF is configured for debugging.
    MIT
  • Switch debugger focus to the specified CPU core. All subsequent debugging actions target that core.
    MIT
  • Lists GDB debugger features including version, build configuration, and available Python modules for debugging and reverse engineering tasks.
    MIT
  • Retrieve current OpenOCD/GDB runtime configuration and value sources to troubleshoot debugging sessions and embedded system issues.
    MIT
  • Stop an active GDB debugging session and release associated resources using the session ID obtained from starting a session.
    MIT
  • Initiate a GDB debugging session and receive a session ID. Supports debugging local programs, core files, attaching to processes, and remote targets.
    MIT
  • Open an interactive GDB console for manual code stepping, allowing joint control with automated debugging tools.
    MIT