cubemx1
Related Servers
Alternatives to cubemx1
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server & Agent Skill for STM32CubeMX 6.x (HAL1). Discover MCU configuration options, parameters and constraints, and compile declarative JSON into .ioc projects offline.1MIT
- AlicenseAqualityBmaintenanceMCP server that wraps STM32CubeMX CLI to let AI load .ioc projects, modify pin/peripheral configurations, generate HAL code, and export pinout tables.536 PyPI3MIT
- AlicenseNot gradedqualityBmaintenanceEnables local stdio-based MCP integration with InoProShop/CODESYS for project structure reading, POU editing with verified writes, compilation, task configuration, and persistent session recovery.4MIT
- AlicenseAqualityDmaintenanceMCP server for debugging STM32 microcontrollers over ST-LINK using STM32CubeCLT tools (GDB, ST-LINK_gdbserver, STM32_Programmer_CLI) with session management, flashing, breakpoints, memory/register access, and expression evaluation.191GPL 3.0
- FlicenseAqualityDmaintenanceMCP server for scaffolding, building, and flashing bare-metal STM32C011 firmware using the STM32CubeCLT toolchain. Exposes tools for project scaffold, build, flash, and probe listing.4-
- AlicenseCqualityBmaintenanceEnables AI clients to create, configure, validate, and generate STM32CubeMX projects through 113 MCP tools, including pin, clock, peripheral, RTOS, and middleware setup plus C code generation. It can drive an installed CubeMX engine or run fully standalone using a bundled data pack with real pin and mode validation.1131MIT
TDQS
Scored across 6 tools
The four .ioc tools form a clear pipeline: import converts .ioc -> target JSON, build converts target JSON -> .ioc, generate runs CubeMX project generation, and check does an acceptance round-trip. The main soft spot is check vs. generate (both involve CubeMX and touching .ioc files, distinguished mainly by the '[acceptance only]' tag) and the very broad probe_describe multiplexer, but descriptions keep them separable.
All tools share the cubemx1_ prefix, but the suffix grammar is mixed: ioc_<verb> (ioc_check, ioc_generate, ioc_import, ioc_build) alongside a bare noun (status) and verb_verb (probe_describe). It reads fine in practice but is not a single predictable pattern.
Six tools is a well-scoped surface for an offline .ioc/target-JSON toolchain, with no obviously redundant entries. Slight imbalance in that probe_describe absorbs five query kinds (describe/boards/peripherals/pins/clock) while others are single-purpose.
The set covers the full conversion lifecycle in both directions, project generation, acceptance verification, session status, and offline discovery of devices/boards/peripherals/pins/clocks. Gaps remain: no tool for editing or patching an existing target JSON (must be hand-authored), no cleanup/removal of generated artifacts, and nothing to compile or run the generated firmware.