STM32 Debug MCP
Related Servers
Alternatives to STM32 Debug MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding assistants to perform complete headless STM32 embedded firmware development, including project creation, pin configuration, code generation, building, and flashing, by driving the official STM32 command-line toolchain.29MIT
- AlicenseNot gradedqualityDmaintenanceAn 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.1MIT
- AlicenseAqualityCmaintenanceThis server enables AI agents to fully control STM32CubeIDE and STMicroelectronics hardware, including GUI automation, headless builds, flashing, GDB debugging, option bytes, serial telemetry, and CubeMX .ioc engineering.342Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI assistants to flash firmware, program memory, modify option bytes, erase chips, reset boards, and capture SWO printf traces for STM32 microcontrollers via STM32CubeCLT.12MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to build, flash, and communicate with STM32 hardware over SWD and serial, including multi-board management, live memory monitoring, and hardware sequences.25MIT
- AlicenseAqualityAmaintenanceEnables AI agents to debug STM32 firmware on real hardware by driving GDB with OpenOCD/ST-Link/J-Link to flash, set breakpoints, inspect memory, registers and RTOS state, triage HardFaults, and profile. Returns decoded, structured evidence and suggested next actions instead of raw GDB text, with composite tools that collapse multi-step debug loops into single calls.862MIT
TDQS
Scored across 35 tools
Tools are grouped into clear subdomains (probe/build/flash, serial, live memory, debug session, WB firmware), and descriptions explicitly distinguish similar paths like stm32_read_memory vs debug_mem vs live_memory_write. A few boundaries remain easy to confuse, especially the multiple memory read/write APIs and build vs build_and_flash, but the set is mostly distinct.
Names consistently use snake_case and family prefixes (stm32_, serial_, live_memory_, debug_), with mostly verb_noun structure. Minor outliers like symbol_info, stm32_board_info, and stm32_build_and_flash keep it from being fully uniform.
35 tools is heavy for one MCP server; while many map to distinct STM32 workflows, the debug, memory, serial, and WB families could be split or consolidated. This exceeds the 25-tool threshold and increases selection overhead.
The surface covers build, flash, probe/board management, serial I/O, live memory, full debug session control, breakpoints/watchpoints, and STM32WB FUS/BLE bringup. Gaps remain around mass erase/option bytes, SWO/ITM trace, source-level stepping, and non-full STM32WB BLE stack variants.