McuBuddy
Related Servers
Alternatives to McuBuddy
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that lets AI tools drive Keil uVision debugging sessions for ARM Cortex-M targets, enabling expression/variable reads, memory access, run control, breakpoints, and trace capture.441MIT
- AlicenseAqualityCmaintenanceStateful MCP server for driving debug probes (J-Link) to flash, debug, and inspect embedded targets. Enables AI agents to perform flash, memory, breakpoint, and ELF/SVD-aware operations conversationally.4133 PyPI10MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for simulating firmware on virtual microcontroller instances, allowing AI agents to upload, run, and read UART output from supported boards such as STM32 and Nordic.17MIT
- AlicenseNot gradedqualityCmaintenanceAn 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
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides comprehensive debugging capabilities for J-Link debuggers, enabling memory, flash, register, and RTT operations through AI assistants.34MIT
- AlicenseBqualityAmaintenanceAgentic Hardware-in-the-Loop (Agentic HIL) lets coding agents develop firmware on real embedded boards: flash, reset, read UART and exchange CAN traffic, diagnose and fix. Local, policy-gated MCP tools support OpenOCD, pyOCD and STM32CubeProgrammer, with pytest for CI.441,560 PyPI17Apache 2.0
TDQS
Scored across 19 tools
Several tools have unclear or overlapping boundaries: configure_probe, probe_connect, and first_contact all relate to probe/debug session startup, while disconnect_all and finish_debug_session both end sessions. match_chip_name and get_target_info also overlap in alias resolution, and some tools have no description at all, making selection risky.
Most tools follow a verb_noun pattern (list_, configure_, get_), but several break it: elf_load, svd_load, and pack_diagnose are noun_verb, and doctor and first_contact are one-off non-pattern names. Overall readable but noticeably inconsistent.
Nineteen tools is on the heavy side for an MCU debug server, and some tools could be consolidated, especially around probe connection and session teardown. Still, the count is not extreme and many tools serve distinct preflight, validation, and configuration purposes.
The tool surface covers setup, probe detection, configuration, ELF/SVD loading, and a few validation/read-only checks, but core MCU debugging operations are missing: no read/write memory, no register access, no step/continue, no breakpoints, and no flash programming. This is a significant gap for a debug-oriented server.