Skip to main content
Glama

Related Servers

Alternatives to esp-runtime-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to directly inspect and debug embedded hardware: reading/writing serial ports and bus devices, auto-detecting baud rates, parsing Modbus/NMEA/custom binary frames, plus diagnosing failures through a 45-rule fault-pattern library, error-code tables, and compile/flash error translation. Also provides pin-conflict checking, register and Cortex-M fault decoding, pre-validated driver and component selection libraries, board knowledge, and guarded flashing with post-flash byte-level verification.
      59
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables local UART and serial-port debugging through MCP, providing persistent capture, log search, regex/event monitoring, HEX send/query, protocol parsing, and shell-like command sequences.
      15
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      This server enables AI coding agents to build, boot, drive and test ESP-IDF firmware in a local ESP32 emulator, capturing UART logs, injecting hardware events, asserting output, and taking screenshots without a physical board or cloud account.
      6
      88 npm
      7
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A headless MCP server that enables AI tools (like Claude Code) to read and analyze serial logs from embedded boards (ESP32, STM32) for firmware debugging, with read-only tools for log retrieval and a built-in web viewer.
      6
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to spawn and control persistent local shells, SSH sessions, REPLs, debuggers, and serial/UART devices with zero-loss output capture, timestamped history, and atomic expect matching for command execution and prompt synchronization.
      12
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Tools target distinct actions: listing ports, capturing logs, analyzing logs, decoding addresses, resetting, reading coredumps. Slight overlap between capture_log (which also parses crashes) and analyze_log, but descriptions clarify the distinction.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (list_serial_ports, capture_log, analyze_log, decode_addresses, reset_device, read_coredump). No mixing of conventions.

    Tool Count5/5

    Six tools form a well-scoped set for ESP runtime debugging: port discovery, log capture, log analysis, address decoding, reset, and coredump reading. Each tool has a clear role without redundancy.

    Completeness4/5

    Core lifecycle for runtime debugging is covered: discovering ports, capturing/analyzing logs, decoding addresses, resetting, and reading coredumps. Minor gaps like device info query or serial write are not critical but could be useful.