ToolBB-0119

McuBuddy: an MCP server for MCU debugging through ST-Link, J-Link and Keil

McuBuddy connects AI assistants to MCU debug probes such as ST-Link and J-Link for board-level debugging. Opt-in toolsets add Keil MDK builds, SVD register decoding, RTT and UART logs, FreeRTOS task state and flash writes. Each result says what kind of failure it found and suggests the next safe check. The README lists validation on STM32L496 and STM32F103 boards.

Open original source github.com · cunjun

Claimed
Why this evidence label?

The author describes it but shows no evidence we could check yet.

How we check entries
Preview image for McuBuddy: an MCP server for MCU debugging through ST-Link, J-Link and Keil
The source's own preview image, from github.com.

Briefing

list_tool_safety() sorts every tool into one of five classes: read-only, execution-changing (halt, reset, step), runtime-state writes, persistent writes such as flash programming, and host processes such as a Keil build. Runtime writes and flash operations need explicit confirmation. Operations on one board are serialized in a session, while sessions for unrelated boards run concurrently. The server runs over stdio only and opens no network listener.

Keil builds and downloads need Windows with Keil MDK, driven through UV4.exe. The probe-rs backend is a preview with no official binary, RTOS views need FreeRTOS symbols that match the firmware, and SVD files usually come from a CMSIS-Pack. The README says implemented code is not validated on every board and points to list_validation_records() for what was tested.

From the GitHub API

Repository facts

Repository facts for cunjun/mcubuddy, from the GitHub API
Repositorycunjun/mcubuddy
Stars8
LicenseMIT Permissive
LanguagePython
Last push17 Aug 2026 2 mo ago

Tags

Board
Instrument

Report a problem with this entry