vscode-cube-mcp
Related Servers
Alternatives to vscode-cube-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that enables AI agents to inspect, plan, validate, and apply STM32CubeMX .ioc configuration changes, and generate STM32CubeIDE projects, ensuring safe and testable embedded-system workflows.91MIT
- 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.34Apache 2.0
- 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
- AlicenseAqualityCmaintenanceMCP 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
- FlicenseAqualityCmaintenanceMCP 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-
- 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.9MIT
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: load reads config, configure applies changes, generate produces code, export_pinout exports CSV. However, cubemx_script is a catch-all escape hatch that can perform all of these operations, which creates some boundary ambiguity for agents deciding between the specific tools and the generic script runner.
All tool names follow the uniform pattern cubemx_<action>, using clear verbs like load, configure, generate, and export_pinout. The naming is perfectly consistent and predictable, with no mixed conventions or vague verbs.
The server has 5 tools, which is well within the ideal 3-15 range for a focused domain. Each tool addresses a distinct CubeMX workflow step, and the number feels appropriate without excess or deficiency.
The tool set covers the core CubeMX lifecycle: loading projects, modifying configuration, generating code, and exporting pinout. Minor gaps exist such as no dedicated tool for creating a new project from scratch or listing all settings, but these can be worked around via the catch-all script tool.