Skip to main content
Glama
Keil5 MCP Server

Keil5 MCP Server

by ZMC1011

Related Servers

Alternatives to Keil5 MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to build, flash, debug, and communicate with STM32 microcontrollers over ST-Link entirely within the conversation. Provides headless CubeIDE builds, OpenOCD flashing, hardware breakpoints, live SWD variable monitoring resolved by C symbol names, fault triage, and pooled serial VCP I/O with deterministic sequencing for hardware-in-the-loop tests.
      35
      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
      A
      quality
      D
      maintenance
      Enables AI assistants to flash firmware, program memory, modify option bytes, erase chips, reset boards, and capture SWO printf traces for STM32 microcontrollers via STM32CubeCLT.
      12
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to build, flash, and debug STM32 projects compiled with Keil MDK-ARM on Windows, returning structured UV4 build diagnostics and evidence-based results. It also provides pyOCD/ST-Link debugging operations such as run control, breakpoints, register/PC reads, and global/static variable inspection.
      29
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      1
      MIT

    TDQS

    C2.9/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (build, source, flash, probe control), and the descriptions help separate them. Minor ambiguity exists between 'probe_resume' and 'continue_target' and between 'parse_build_errors' and 'explain_build_error', but these are usable with the provided docs.

    Naming Consistency3/5

    The majority follow a verb_noun pattern like 'build_project', 'source_edit', and 'probe_halt', but there are notable deviations such as 'uv4_debug_dde', 'keil_doctor', and 'build_progress_status'. Names are generally readable but the mixed styles prevent a higher score.

    Tool Count2/5

    With 27 tools, the server exceeds the 25+ threshold where tool count becomes heavy for an agent to navigate. The tools cover many subdomains, but several low-level probe primitives and debug-session helpers could be consolidated or omitted.

    Completeness3/5

    The server covers build, source editing, flashing, and basic debugging well. However, obvious lifecycle gaps exist: breakpoints can be set but not listed/deleted, memory/registers are read-only, and there is no standalone reset target operation or project creation/configuration update capability.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data