ToolBB-0062

OpenOCD MCU MCP: an OpenOCD bridge and Codex skill for Cortex-M debugging

OpenOCD MCU MCP connects a coding agent to a microcontroller through OpenOCD, using an MCP server and a Codex skill. The agent can identify the chip, halt and reset it, read registers and memory, and decode peripheral registers from CMSIS-SVD files. The README includes a smoke test on an STM32F407 over a CMSIS-DAP probe.

Open original source github.com · Michael Law

Shown working
Why this evidence label?

README and examples/stm32f407-cmsis-dap-smoke-test.md show output from a real STM32F407 over CMSIS-DAP: CPUID 0x410FC241, DEV_ID 0x413 and RCC_CR read and decoded.

How we check entries
Preview image for OpenOCD MCU MCP: an OpenOCD bridge and Codex skill for Cortex-M debugging
The source's own preview image, from github.com.

Briefing

The project drives OpenOCD through its telnet port, and the README expects it to work with any probe OpenOCD supports; only CMSIS-DAP has been tested. Its 12 MCP tools include probe_chip, register_read, memory_write, find_svd and decode_register. The bundled skill routes HardFaults, hangs, clock and memory faults to a playbook. It has no third-party Python dependencies.

MCP tools act directly on the target, so the README advises using them only where changing run state or memory is acceptable. The CLI asks for confirmation flags before writes, resets and resumes. Testing so far is Windows with PowerShell and OpenOCD 0.12.0. The smoke-test output shows CPUID 0x410FC241, DEV_ID 0x413 and a decoded RCC_CR value.

From the GitHub API

Repository facts

Repository facts for royforlinux/openocd-mcu-mcp, from the GitHub API
Repositoryroyforlinux/openocd-mcu-mcp
Stars5
LicenseMIT Permissive
LanguagePython
Last push24 May 2026 5 mo ago

Tags

Board
Instrument
Agent

Report a problem with this entry