Skip to main content
Glama
Sign In
mcu-debug-mcp

mcu-debug-mcp

by stillsurge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcu-debug-mcp

No user-submitted related servers found.

    Related Servers

    • hardware-tooling-mcp

      Pheem49
      A
      license
      A
      quality
      C
      maintenance
      Gives AI agents direct hands-on access to physical hardware and host OS resources over local stdio: serial monitoring with crash-dump detection, firmware compile/flash via arduino-cli, PlatformIO, ESP-IDF and esptool, direct GPIO/I2C/SPI over FTDI bridges, BLE GATT operations, webcam or microscope snapshots, logic analyzer captures, audio recording and test tones, GUI screenshots and hotkeys, and Android ADB commands. It also helps diagnose toolchain and serial-permission problems and identify or terminate processes that lock a port.
      33
      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

    • embedded-mcp

      SunstanYu
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to compile, flash, erase, and read serial output from embedded development boards, with guardrails such as budget limits, serial port mutexes, and mandatory human confirmation for destructive operations.
      5
      -

    • STM32 GDB MCP Server

      Zeraissh
      A
      license
      A
      quality
      B
      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
      3
      MIT

    • em-debug MCP Server

      RoadToSea
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to debug and inspect embedded ARM Cortex-M and RISC-V targets through probe-rs — execution control, memory inspection, live CoreSight AP access, firmware-free peripheral bringup, and crash/fault decoding — without external GDB or OpenOCD, and while sharing a single hardware session with a human's VS Code debug session. It runs both embedded in the VS Code extension and headless over Streamable HTTP or stdio for CI/CD and terminal agents.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.5/5.0

    Scored across 59 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and descriptions explicitly clarify overlaps such as serial_read vs stream_capture and analyze_log vs error_code_lookup. However, with 59 tools, some subtle boundary cases remain (e.g., driver_get vs component_get, pinmap_get vs pin_check), so perfect disambiguation is not achieved.

    Naming Consistency4/5

    Names uniformly use snake_case with helpful domain prefixes (serial_, i2c_, spi_, modbus_), making related tools easy to group. There is a minor inconsistency: some tools use noun_verb (pinmap_list, board_get) while others use verb_noun (decode_register, analyze_log), but the overall pattern is still readable and predictable.

    Tool Count1/5

    59 tools is excessive for a single MCP server, far exceeding the typical 3-15 sweet spot and even the 25+ threshold for 'too many.' Even given the broad MCU debugging scope, this count creates significant selection overhead and many tools could be consolidated or made optional.

    Completeness4/5

    The tool surface is very comprehensive, covering hardware bring-up, serial protocols, flashing, fault decoding, register/map analysis, and knowledge bases. Minor gaps exist for live debugging (breakpoints, stepping), CAN bus, and direct memory read/write, but core workflows are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources