io.github.microhenrio/openocd-mcp
Related Servers
Alternatives to io.github.microhenrio/openocd-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceStateful MCP server for driving debug probes (J-Link) to flash, debug, and inspect embedded targets. Enables AI agents to perform flash, memory, breakpoint, and ELF/SVD-aware operations conversationally.4110MIT
- AlicenseAqualityDmaintenanceEnables AI assistants like Claude to directly debug microcontrollers via JLink, supporting breakpoints, single-step, memory/register access, variable inspection, RTT logging, and firmware flashing.255MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI coding agents drive the full STM32 development loop—code generation, build, flash, debug, serial monitoring, and fault diagnosis—end to end via CubeIDE, CubeMX, CubeProgrammer, OpenOCD, and GDB.MIT
- AlicenseAqualityCmaintenanceMCP 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.343MIT
- FlicenseAqualityBmaintenanceA headless MCP server that enables AI tools (like Claude Code) to read and analyze serial logs from embedded boards (ESP32, STM32) for firmware debugging, with read-only tools for log retrieval and a built-in web viewer.6-

sbl-debuggerofficial
AlicenseNot gradedqualityDmaintenanceEnables AI assistants to debug ARM Cortex-M targets via GDB and OpenOCD, supporting attach, breakpoints, stepping, register/memory inspection, and SVD peripheral decoding.MIT
TDQS
Scored across 39 tools
Each tool has a clearly distinct purpose, from setting breakpoints and watchpoints to reading/writing memory, registers, peripherals, and variables. There is no overlapping functionality; even the raw command escape hatch is explicitly for uncovered operations.
All tools follow a consistent verb_noun or verb_noun pattern using snake_case (e.g., add_breakpoint, read_memory, flash_write). Single-word verbs like halt and reset are common for core actions. The naming makes tool selection intuitive.
With 39 tools, the count is high but justified by the broad scope of microcontroller debugging (breakpoints, watchpoints, memory, registers, peripherals, variables, flashing, configuration, etc.). It covers all typical needs without being bloated, though a few tools could be combined.
The tool surface covers all essential debugging operations: breakpoints (including conditional and watchpoints), memory/register/peripheral access, variable read/write with ELF symbol loading, flashing, reset, resume, step, status, configuration, permissions, and a raw command escape hatch. No critical gaps are apparent.