Z
Zeraissh/stm32-gdb-mcp
MCP server that lets AI agents debug STM32 firmware on real hardware (GDB + OpenOCD/ST-Link/J-Link): HardFault triage, FreeRTOS, SWO/RTT, decoded structured results.
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"zeraissh-stm32-gdb-mcp": {
"command": "uvx",
"args": ["stm32-gdb-mcp"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"zeraissh-stm32-gdb-mcp": {
"command": "uvx",
"args": ["stm32-gdb-mcp"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio zeraissh-stm32-gdb-mcp -- uvx stm32-gdb-mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 4 ★ · Zeraissh/stm32-gdb-mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 4 ★ · 23 sources · mcp
- Install
uvx stm32-gdb-mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
uvx stm32-gdb-mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Zeraissh/stm32-gdb-mcp；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# STM32 GDB MCP Server / STM32 GDB MCP 服务器
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
An MCP server that lets an AI agent debug STM32 firmware on real hardware — drive
GDB + OpenOCD/ST-Link/J-Link to flash, breakpoint, inspect memory/registers/RTOS, triage
HardFaults, and profile — and get back decoded, structured evidence instead of raw GDB text.
让 AI 智能体在真实硬件上调试 STM32:通过 GDB + OpenOCD/ST-Link/J-Link 烧录、打断点、查
内存/寄存器/RTOS、定位 HardFault、做性能采样,返回已解码的结构化证据而非原始 GDB 文本。
bash
uvx stm32-gdb-mcp # any MCP client: command "uvx", args ["stm32-gdb-mcp"]
Needs arm-none-eabi-gdb (or gdb-multiarch) and a GDB server (OpenOCD / J-Link / st-util)
on PATH; stm32-gdb-mcp-check-env prints the install command for your OS. See
Install for one-command setup in Claude Code, Cursor, VSCode and others.
/ 需要 PATH 中有 arm-none-eabi-gdb（或 gdb-multiarch）和一种 GDB Server；
stm32-gdb-mcp-check-env 会给出本机系统的安装命令。各客户端的一键安装见下方 Install。
## Why this server / 为什么选它
| | Generic GDB MCP servers / 通用 GDB MCP | probe-rs-based servers / 基于 probe-rs | stm32-gdb-mcp |
| Output / 返回内容 | Raw GDB text / 原始文本 | Structured / 结构化 | Decoded + suggestednextactions / 解码结果 + 下一步建议 |
| HardFault → source line / 定位到源码 | — | ✓ | ✓ plus stack analysis / 附栈分析 |
| FreeRTOS tasks, stacks, queues / RTOS 感知 | — | — | ✓ |
| Peripheral registers decoded from SVD / SVD 外设解码 | — | — | ✓ |
| Logs / 日志 | — | RTT | RTT, SWO, UART |
| Symbolized PC sampling / 符号化采样 | — | — | ✓ |
| One-call bring-up (flashandrun, debuguntil) / 组合工具 | — | partial / 部分 | ✓ |
| Replay + debug report / 回放与报告 | — | — | ✓ |
| Multi-board rack, programmable USB hub / 多板与 USB Hub | — | — | ✓ |
| Probes / 调试器 | Any GDB remote | probe-rs probes | ST-Link, J-Link, CMSIS-DAP via OpenOCD / J-Link GDB Server / st-util |
| Targets / 目标芯片 | Any | Cortex-M, RISC-V, ESP32 | STM32 (Cortex-M) |
Pick a probe-rs-based server if you need RISC-V or ESP32; pick this one when you debug STM32
and want the agent to get from symptom to root cause with fewer calls.
/ 需要 RISC-V 或 ESP32 时选 probe-rs 系；调试 STM32、希望 agent 用更少调用从现象走到根因时选本项目。
## What you get / 能力一览
| Bring-up & flash / 启动与烧录 | detectprobe, suggestserverargs, buildfirmware, flashandrun, selfcheck, resettarget |
| Execution / 执行控制 | runandwait（结构化停止事件）, runforduration（运行/采样后暂停并采集）, breakpoint, step, halt/continue, debuguntil |
| Inspect / 状态检查（需暂停） | capturestate, readmemory/readvariable, readregisters, frame, readperipheralregister |
| Fault triage / 故障诊断 | reconstructfaultcontext（故障 PC → 源码）, diagnosefault, analyzestack |
| RTOS / 实时系统 | detectrtos, readfreertos, snapshot(scope=rtos) |
| Observe / 可观测性 | logging（RTT/SWO/UART）, setupswo（无需额外解码器的 printf）, samplepc（符号化采样器） |
| Determinism / 可复现性 | runscenario（回放）, batch, getsession 日志/指标, exportdebugreport |
| Multi-board / 多板卡 | 任意工具传 session="name"；使用 listsessions/closesession 管理 |
Two cross-cutting goals: low comprehension cost (decoded outputs, suggestednextactions)
and minimal repro steps (composites like flashandrun / debuguntil collapse 5–15 calls
into one). Compact mode keeps the visible surface small; every tool remains reachable through
call(tool, args), and toolhelp exposes hidden schemas.
两个贯穿目标是：通过解码结果和 suggestednextactions 降低理解成本，并通过
flashandrun、debuguntil 等组合工具把多次调用压缩为一次，缩短复现路径。
compact 模式只展示核心工具；所有隐藏工具仍可由 call(tool, args) 调用，并可用
GDB + OpenOCD/ST-Link/J-Link to flash, breakpoint, inspect memory/registers/RTOS, triage
HardFaults, and profile — and get back decoded, structured evidence instead of raw GDB text.
让 AI 智能体在真实硬件上调试 STM32:通过 GDB + OpenOCD/ST-Link/J-Link 烧录、打断点、查
内存/寄存器/RTOS、定位 HardFault、做性能采样,返回已解码的结构化证据而非原始 GDB 文本。
bash
uvx stm32-gdb-mcp # any MCP client: command "uvx", args ["stm32-gdb-mcp"]
Needs arm-none-eabi-gdb (or gdb-multiarch) and a GDB server (OpenOCD / J-Link / st-util)
on PATH; stm32-gdb-mcp-check-env prints the install command for your OS. See
Install for one-command setup in Claude Code, Cursor, VSCode and others.
/ 需要 PATH 中有 arm-none-eabi-gdb（或 gdb-multiarch）和一种 GDB Server；
stm32-gdb-mcp-check-env 会给出本机系统的安装命令。各客户端的一键安装见下方 Install。
## Why this server / 为什么选它
| | Generic GDB MCP servers / 通用 GDB MCP | probe-rs-based servers / 基于 probe-rs | stm32-gdb-mcp |
| Output / 返回内容 | Raw GDB text / 原始文本 | Structured / 结构化 | Decoded + suggestednextactions / 解码结果 + 下一步建议 |
| HardFault → source line / 定位到源码 | — | ✓ | ✓ plus stack analysis / 附栈分析 |
| FreeRTOS tasks, stacks, queues / RTOS 感知 | — | — | ✓ |
| Peripheral registers decoded from SVD / SVD 外设解码 | — | — | ✓ |
| Logs / 日志 | — | RTT | RTT, SWO, UART |
| Symbolized PC sampling / 符号化采样 | — | — | ✓ |
| One-call bring-up (flashandrun, debuguntil) / 组合工具 | — | partial / 部分 | ✓ |
| Replay + debug report / 回放与报告 | — | — | ✓ |
| Multi-board rack, programmable USB hub / 多板与 USB Hub | — | — | ✓ |
| Probes / 调试器 | Any GDB remote | probe-rs probes | ST-Link, J-Link, CMSIS-DAP via OpenOCD / J-Link GDB Server / st-util |
| Targets / 目标芯片 | Any | Cortex-M, RISC-V, ESP32 | STM32 (Cortex-M) |
Pick a probe-rs-based server if you need RISC-V or ESP32; pick this one when you debug STM32
and want the agent to get from symptom to root cause with fewer calls.
/ 需要 RISC-V 或 ESP32 时选 probe-rs 系；调试 STM32、希望 agent 用更少调用从现象走到根因时选本项目。
## What you get / 能力一览
| Bring-up & flash / 启动与烧录 | detectprobe, suggestserverargs, buildfirmware, flashandrun, selfcheck, resettarget |
| Execution / 执行控制 | runandwait（结构化停止事件）, runforduration（运行/采样后暂停并采集）, breakpoint, step, halt/continue, debuguntil |
| Inspect / 状态检查（需暂停） | capturestate, readmemory/readvariable, readregisters, frame, readperipheralregister |
| Fault triage / 故障诊断 | reconstructfaultcontext（故障 PC → 源码）, diagnosefault, analyzestack |
| RTOS / 实时系统 | detectrtos, readfreertos, snapshot(scope=rtos) |
| Observe / 可观测性 | logging（RTT/SWO/UART）, setupswo（无需额外解码器的 printf）, samplepc（符号化采样器） |
| Determinism / 可复现性 | runscenario（回放）, batch, getsession 日志/指标, exportdebugreport |
| Multi-board / 多板卡 | 任意工具传 session="name"；使用 listsessions/closesession 管理 |
Two cross-cutting goals: low comprehension cost (decoded outputs, suggestednextactions)
and minimal repro steps (composites like flashandrun / debuguntil collapse 5–15 calls
into one). Compact mode keeps the visible surface small; every tool remains reachable through
call(tool, args), and toolhelp exposes hidden schemas.
两个贯穿目标是：通过解码结果和 suggestednextactions 降低理解成本，并通过
flashandrun、debuguntil 等组合工具把多次调用压缩为一次，缩短复现路径。
compact 模式只展示核心工具；所有隐藏工具仍可由 call(tool, args) 调用，并可用
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/zeraissh-stm32-gdb-mcp/)
- Source
- awesome · https://github.com/Zeraissh/stm32-gdb-mcp
- Browse by field
- MCP servers
- Traction
- 4 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.