Skip to main content
Glama
Sign In
keil-mdk-mcp

keil-mdk-mcp

by lideshengstu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to keil-mdk-mcp

No user-submitted related servers found.

    Related Servers

    • STM32 GDB MCP Server

      Zeraissh
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to debug STM32 firmware on real hardware by driving GDB with OpenOCD/ST-Link/J-Link to flash, set breakpoints, inspect memory, registers and RTOS state, triage HardFaults, and profile. Returns decoded, structured evidence and suggested next actions instead of raw GDB text, with composite tools that collapse multi-step debug loops into single calls.
      86
      2
      MIT

    • MCUDebugforAI

      SingleDemo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to compile, debug, sample, and inspect MCU firmware through J-Link/pyOCD or a mock engine, including breakpoints, watchpoints, single-stepping, register access, and flash dump operations.
      MIT

    • STM32 Debug MCP

      YuriAlvesBordin
      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

    • Keil5 MCP Server

      ZMC1011
      A
      license
      C
      quality
      C
      maintenance
      Enables AI coding agents to build, flash, debug, and read feedback from STM32 development projects in Keil MDK, forming a closed loop to automatically fix code.
      27
      9
      MIT

    • pyocd-debug-mcp

      konbakuyomu
      A
      license
      A
      quality
      C
      maintenance
      Enables AI tools to perform full-featured embedded microcontroller debugging via pyOCD and CMSIS-DAP probes, including probe management, flashing, breakpoints, register/memory access, fault analysis, and RTT communication.
      58
      2
      MIT

    • STM32Cube-MCP

      brovk2008
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.9/5.0

    Scored across 29 tools

    Disambiguation3/5

    Most tools map to a distinct resource+action, but there are near-duplicate pairs: keil_read_variable vs keil_read_variables (singular vs batch) and keil_get_status vs keil_get_execution_state vs keil_get_pc, which an agent could easily misselect. The three source-level step tools (step_into/step_over/step_out) all return 'unsupported' and overlap functionally with keil_step_instruction, adding noise rather than clarity.

    Naming Consistency4/5

    All 29 tools use a consistent keil_ prefix plus verb_noun form (get_*, read_*, set_*, step_*, build/rebuild/flash), which is highly predictable. The only blemish is the singular/plural pair keil_read_variable / keil_read_variables, where the names differ by one character but describe different scopes.

    Tool Count2/5

    At 29 tools the surface is heavy for a single debug/build server, and several slots are effectively placeholders: keil_step_into, keil_step_over, keil_step_out and keil_get_call_stack exist only to report 'not implemented'. Trimming those and folding status/execution-state queries together would bring it into a reasonable scope.

    Completeness3/5

    Core lifecycle is covered: project info, build/rebuild/logs/error parsing, flash, connect/disconnect, reset/run/halt, breakpoint CRUD, register/variable reads, and diagnostics. However, source-level stepping and call-stack unwinding are explicitly absent, and there is no memory or register write, no expression/watch evaluation, and no peripheral access, leaving common debug workflows with dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources