Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

STM32 GDB Debugger

by Zeraisshversion 0.15.1i★ 3iRuns on your computerRepository ↗
Registry nameio.github.Zeraissh/stm32-gdb-mcp

How to install

What it does

Debug STM32 firmware on real hardware via GDB + OpenOCD/ST-Link/J-Link with decoded results.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity7/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score19/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install STM32 GDB Debugger. Follow https://mcp.popnx.com/i/zeraissh-stm32-gdb-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server STM32 GDB Debugger for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "stm32-gdb": { "command": "uvx", "args": [ "stm32-gdb-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the STM32 GDB Debugger tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "stm32-gdb": {
          "command": "uvx",
          "args": [
            "stm32-gdb-mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use STM32 GDB Debugger and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using STM32 GDB Debugger or shows a STM32 GDB Debugger tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • STM32_GDB_MCP_COMPACT Set to 1 to expose only the core tools; every other tool stays reachable through call(tool, args). · default 1

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect STM32 GDB Debugger yet

STM32 GDB Debugger runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect STM32 GDB Debugger

  • Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server STM32 GDB Debugger for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user stm32-gdb -- uvx stm32-gdb-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the STM32 GDB Debugger tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user stm32-gdb -- uvx stm32-gdb-mcp
  4. Type /mcp in Claude Code

    You should see STM32 GDB Debugger listed as connected

  5. Try it

    Use STM32 GDB Debugger and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using STM32 GDB Debugger or shows a STM32 GDB Debugger tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • STM32_GDB_MCP_COMPACT Set to 1 to expose only the core tools; every other tool stays reachable through call(tool, args). · default 1

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server STM32 GDB Debugger for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "stm32-gdb": { "command": "uvx", "args": [ "stm32-gdb-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the STM32 GDB Debugger tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use STM32 GDB Debugger and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using STM32 GDB Debugger or shows a STM32 GDB Debugger tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • STM32_GDB_MCP_COMPACT Set to 1 to expose only the core tools; every other tool stays reachable through call(tool, args). · default 1

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server STM32 GDB Debugger for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "stm32-gdb": { "type": "stdio", "command": "uvx", "args": [ "stm32-gdb-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the STM32 GDB Debugger tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use STM32 GDB Debugger and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using STM32 GDB Debugger or shows a STM32 GDB Debugger tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • STM32_GDB_MCP_COMPACT Set to 1 to expose only the core tools; every other tool stays reachable through call(tool, args). · default 1

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use STM32 GDB Debugger💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user stm32-gdb -- uvx stm32-gdb-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "stm32-gdb": {
      "command": "uvx",
      "args": [
        "stm32-gdb-mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "stm32-gdb": {
      "command": "uvx",
      "args": [
        "stm32-gdb-mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "stm32-gdb": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "stm32-gdb-mcp"
      ]
    }
  }
}

Values you fill in

  • STM32_GDB_MCP_COMPACT env
    Set to 1 to expose only the core tools; every other tool stays reachable through call(tool, args).

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
36/wk
Connection
Runs on your computer
Latest versioni
0.15.1
Categoryi
Other
Published to registryi
Oct 19, 2026
Code last changedi
Oct 24, 2026
Maker
Zeraissh
Packages
pypi: stm32-gdb-mcp
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Zeraissh, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 26 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for stm32-gdb-mcp@0.15.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/zeraissh-stm32-gdb-mcp.svg)](https://mcp.popnx.com/en/servers/zeraissh-stm32-gdb-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 93% of the other 20693 servers in this category
  • Published to the registry more recently than 58% of the other 20693 servers in this category
  • Basic checks equal to or better than 99% of the other 20693 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is STM32 GDB Debugger safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 26 days ago, and the latest version (0.15.1) reached the registry 31 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
STM32 GDB Debugger
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

STM32 GDB MCP Server / STM32 GDB MCP 服务器

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 文本。

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 MCPprobe-rs-based servers / 基于 probe-rsstm32-gdb-mcp
Output / 返回内容Raw GDB text / 原始文本Structured / 结构化Decoded + suggested_next_actions / 解码结果 + 下一步建议
HardFault → source line / 定位到源码—✓✓ plus stack analysis / 附栈分析
FreeRTOS tasks, stacks, queues / RTOS 感知——✓
Peripheral registers decoded from SVD / SVD 外设解码——✓
Logs / 日志—RTTRTT, SWO, UART
Symbolized PC sampling / 符号化采样——✓
One-call bring-up (flash_and_run, debug_until) / 组合工具—partial / 部分✓
Replay + debug report / 回放与报告——✓
Multi-board rack, programmable USB hub / 多板与 USB Hub——✓
Probes / 调试器Any GDB remoteprobe-rs probesST-Link, J-Link, CMSIS-DAP via OpenOCD / J-Link GDB Server / st-util
Targets / 目标芯片AnyCortex-M, RISC-V, ESP32STM32 (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 / 启动与烧录detect_probe, suggest_server_args, build_firmware, flash_and_run, self_check, reset_target
Execution / 执行控制run_and_wait(结构化停止事件), run_for_duration(运行/采样后暂停并采集), breakpoint, step, halt/continue, debug_until
Inspect / 状态检查(需暂停)capture_state, read_memory/read_variable, read_registers, frame, read_peripheral_register
Fault triage / 故障诊断reconstruct_fault_context(故障 PC → 源码), diagnose_fault, analyze_stack
RTOS / 实时系统detect_rtos, read_freertos, snapshot(scope=rtos)
Observe / 可观测性logging(RTT/SWO/UART), setup_swo(无需额外解码器的 printf), sample_pc(符号化采样器)
Determinism / 可复现性run_scenario(回放), batch, get_session 日志/指标, export_debug_report
Multi-board / 多板卡任意工具传 session="name";使用 list_sessions/close_session 管理

Two cross-cutting goals: low comprehension cost (decoded outputs, suggested_next_actions) and minimal repro steps (composites like flash_and_run / debug_until collapse 5–15 calls into one). Compact mode keeps the visible surface small; every tool remains reachable through call(tool, args), and tool_help exposes hidden schemas.

两个贯穿目标是:通过解码结果和 suggested_next_actions 降低理解成本,并通过 flash_and_run、debug_until 等组合工具把多次调用压缩为一次,缩短复现路径。 compact 模式只展示核心工具;所有隐藏工具仍可由 call(tool, args) 调用,并可用 tool_help 查询完整说明与 schema。

Install / 安装

ClientOne command
Claude Code(工具 + skills + 常驻规则)/plugin marketplace add Zeraissh/stm32-gdb-mcp,然后 /plugin install stm32-debug-kit@zeraissh-stm32
Cursor / VSCode / Codex / Windsurf / Traepython scripts/deploy.py --project " " --ide vscode,cursor
Manual / 手动配置(任意 MCP 客户端)pip install -e .,再将客户端指向 stm32-gdb-mcp

deploy.py installs the server, writes the IDE's MCP config, and drops a project-aware rules file into your firmware project. Per-client config snippets + the rules template are in docs/install-ides.md. Compact mode is on by default. PyPI/console installs also expose stm32-gdb-mcp-check-env, stm32-gdb-mcp-install, and stm32-gdb-mcp-deploy.

deploy.py 会安装服务器、写入 IDE 的 MCP 配置,并在固件项目中生成带项目上下文的规则文件。 各客户端配置片段和规则模板见 docs/install-ides.md。默认启用 compact 模式;PyPI/console 安装还会提供上述三个辅助命令。

stm32-gdb-mcp-check-env --json also reports the imported module version/path, installed distribution version, and all four console scripts. Use stm32-gdb-mcp-deploy --upgrade when those installation fields drift. / stm32-gdb-mcp-check-env --json 还会报告当前导入 模块的版本/路径、已安装发行版本和四个 console script;这些安装字段发生漂移时,使用 stm32-gdb-mcp-deploy --upgrade 修复。

Requirements / 环境要求:PATH 中需要 arm-none-eabi-gdb(Debian/Ubuntu 上的 gdb-multiarch 也可以,或用 STM32_GDB_MCP_GDB 指定任意支持 ARM 的 GDB),以及至少一种 GDB Server(openocd / JLinkGDBServerCL / st-util)。运行 stm32-gdb-mcp-check-env(或 python setup_env.py)检查;缺什么,它会打印本机系统(Windows scoop / macOS brew / Linux apt、pacman)对应的一行安装命令。 Needs arm-none-eabi-gdb (or gdb-multiarch, or any ARM-capable GDB named by STM32_GDB_MCP_GDB) plus one GDB server; stm32-gdb-mcp-check-env prints the install command for whatever is missing on your OS.

What the plugin runs and connects to / 插件会运行和连接什么

The Claude Code plugin (stm32-debug-kit) runs everything locally on your machine:

  • MCP server: python scripts/run_mcp_server.py, which runs the server from this repository's src/ over stdio. The Python it runs under needs the dependencies in pyproject.toml (pip install -e . or pip install stm32-gdb-mcp).
  • SessionStart hook: python hooks/session_start.py prints a short banner into the session context. It reads nothing and sends nothing.
  • Processes it starts: arm-none-eabi-gdb (or the GDB named above), a GDB server (openocd, JLinkGDBServerCL or st-util), and, when you ask it to build, cmake/make. They talk to the debug probe over USB and to each other over TCP on localhost.
  • Local ports: GDB server ports on localhost; the optional USB hub daemon and dashboard serve on 127.0.0.1 only (default port 8765). Serial ports are opened only when a tool reads a UART log.
  • Files: it reads your firmware project (ELF, SVD, build files). It writes only where a tool is told to (a debug report, a saved debug config), plus small lock and state files under the system temp folder (stm32-gdb-mcp/).
  • Network: nothing leaves your machine unless an agent calls report_issue, which files a GitHub issue on Zeraissh/stm32-gdb-mcp through your own gh CLI login. That issue contains the description the agent wrote, the MCP version and environment summary, and the session's tool journal and metrics. There is no telemetry.

Claude Code 插件(stm32-debug-kit)的所有内容都在本机运行:

  • MCP 服务器:python scripts/run_mcp_server.py,通过 stdio 运行本仓库 src/ 中的服务器。 运行它的 Python 需要装好 pyproject.toml 中的依赖(pip install -e . 或 pip install stm32-gdb-mcp)。
  • SessionStart hook:python hooks/session_start.py 只向会话上下文输出一段简短说明, 不读取也不发送任何数据。
  • 启动的进程:arm-none-eabi-gdb(或上文指定的 GDB)、GDB Server(openocd、JLinkGDBServerCL 或 st-util),以及按需构建时的 cmake/make。它们通过 USB 连接调试器,彼此之间通过 localhost 上的 TCP 通信。
  • 本地端口:GDB Server 端口只在 localhost;可选的 USB Hub 守护进程和看板只监听 127.0.0.1(默认端口 8765)。只有在工具读取 UART 日志时才会打开串口。
  • 文件:读取你的固件工程(ELF、SVD、构建文件)。只在工具指定的位置写文件(调试报告、 保存的调试配置),另外在系统临时目录的 stm32-gdb-mcp/ 下写少量锁文件和状态文件。
  • 网络:除非 agent 调用 report_issue,否则不会有数据离开本机。report_issue 会用你 本机 gh CLI 的登录身份,在 Zeraissh/stm32-gdb-mcp 上提交一个 GitHub issue,内容包括 agent 写的描述、MCP 版本和环境摘要,以及本次会话的工具调用记录和指标。没有任何遥测。

30-second quickstart / 快速上手

detect_probe()                                           # USB evidence; auto-select only one probe

debug_profile(action=set, mcu="STM32L431", probe="stlink", elf_path="build/app.elf", svd_path="STM32L4.svd") suggest_server_args(mcu="STM32L431") # probe omitted -> use profile probe start_debug_session(server_type="openocd") # server_args omitted -> infer from profile mcu/probe self_check() # ALWAYS first: byte order, core, family flash_and_run(file_path="build/app.elf", run_to="main") breakpoint(action=set, location="my_func", condition="state == BAD") run_and_wait() # structured stop event + next actions run_for_duration(duration_sec=30, capture={"expressions": ["rx_count"]}) run_for_duration(duration_sec=60, sample={"interval_ms": 500, "expressions": ["rx_count", "state"]}) reconstruct_fault_context() # on a crash: faulting PC → file:line

detect_probe reads physical USB devices, keeps serials for identical probes, and never chooses between multiple connected probes. / detect_probe 读取真实 USB 设备,同型号探针按 序列号分别保留;连接多个探针时绝不会擅自选择。

The full tool reference (lean families with action=/what=) is skills/stm32-debug/reference/tool-map.md. The server also ships always-on instructions, so any MCP client gets the debug loop without setup.

完整工具索引见 skills/stm32-debug/reference/tool-map.md, 其中按 action= / what= 归并工具族。服务器还会发送常驻 instructions,因此任意 MCP 客户端连接后都能获得同一套调试闭环。

Key rules (the target must cooperate) / 关键规则

  • Reads need a HALTED core. If a read says target_unresponsive, halt_execution first. / 读取要求内核已暂停。 若返回 target_unresponsive,先执行 halt_execution。
  • run_for_duration(sample=...) is best-effort low-rate debugger polling. It does not halt the target itself, but running-target expression reads may fail on some probes/MCUs; use SWO/ring-buffer firmware telemetry for higher-rate or guaranteed capture. / run_for_duration(sample=...) 是尽力而为的低速调试器轮询;某些探针或 MCU 无法在运行中读取 表达式。需要更高采样率或可靠采集时,请使用 SWO 或固件环形缓冲。
  • A breakpoint TIMEOUT means the path was NOT reached — don't just retry. Halt, capture_state, breakpoint(action=list) (hit_count=0 confirms), read the gating flag, set an earlier breakpoint or drive the precondition. / 断点超时表示路径没有到达。 不要原样重试;暂停后采集状态、确认 命中次数、读取门控条件,再前移断点或驱动前置条件。
  • Writes are guarded (option bytes/IWDG/WWDG blocked) — write_guard(action=policy) to allow. / 写操作受保护。 option bytes、IWDG、WWDG 默认禁止,需用 write_guard(action=policy) 显式放行。
  • Never hard-kill OpenOCD (wedges the ST-Link USB) — use recover_session. SWD is exclusive. / 不要强杀 OpenOCD。 使用 recover_session;同一探针的 SWD 调试连接是独占的。
  • A wedged probe needs a physical re-enumeration. With the optional [hub] extra and a SmartUSBHub, hub(action=power) cuts VBUS and hub(action=data) drops the USB data lines, so that re-plug becomes a tool call. Without a hub it is still a hum

Only the beginning is shown; read the rest in the repo