Skip to main content
Glama

Related Servers

Alternatives to mxmcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server that wraps STM32CubeMX CLI to let AI load .ioc projects, modify pin/peripheral configurations, generate HAL code, and export pinout tables.
      5
      46 PyPI
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      4
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely modify STM32CubeMX .ioc configurations, generate code, and verify that intended peripherals and pins actually appear in the generated output. It provides tools for generation verification, .ioc backup and restore, and key-value editing under path allowlists and read-only write policies.
      95 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An 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.
      9
      7
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      This 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.
      34
      2
      Apache 2.0

    TDQS

    C2.9/5.0

    Scored across 113 tools

    Disambiguation2/5

    The set has many overlapping paths to the same outcome: `cli` can perform nearly every other operation, while `standalone_*` tools mirror the main project/pin/mode/parameter workflow. Additional overlaps exist between `project_diff` and `ioc_compare`, `verify` and `compliance`, `project_create` and `standalone_create`, and different search/list tools for MCUs, boards, and signals.

    Naming Consistency3/5

    Most tools use lower snake_case and many share a clear domain prefix such as `project_`, `pin_`, `mode_`, `clock_`, and `standalone_`. However, action ordering and granularity vary between noun_verb, verb_noun, bare abbreviations, and noun-only names (`generate_code`, `project_generate`, `swmgr`, `login`, `rtos_status`, `middleware_add`).

    Tool Count1/5

    113 tools is far beyond an appropriate MCP surface for a single server, even for a complex CubeMX automation domain. The duplicate standalone path, generic CLI escape hatches, and many specialized query/mutate pairs make the set unwieldy for agent tool selection.

    Completeness5/5

    The surface covers project lifecycle, MCU/board discovery, pinout, modes, IP parameters, clocks, generation, packs, software packages, authentication, DMA/MDMA/GIC/NVIC, RTOS, middleware, standalone operation, and verification. There are no obvious major lifecycle or CRUD gaps for CubeMX configuration and generation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues