Skip to main content
Glama
gurul

hardware-logging

by gurul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hardware-logging

No user-submitted related servers found.

    Related Servers

    • BYO Server

      JasonPeng2019
      F
      license
      A
      quality
      B
      maintenance
      Headless local stdio MCP server for board-debug operations, allowing compatible clients to use tools for firmware debugging and board management.
      20
      4
      -

    • Firmware MCP Server

      Alooswr
      A
      license
      Not graded
      quality
      D
      maintenance
      A local stdio MCP server for embedded firmware automation that exposes tools to build, flash, reset devices, and capture serial logs through a device configuration file.
      1
      MIT

    • agentic-hil

      agentic-hil
      A
      license
      A
      quality
      A
      maintenance
      Agentic Hardware-in-the-Loop (Agentic HIL) lets coding agents develop firmware on real embedded boards: flash, reset, read UART and exchange CAN traffic, diagnose and fix. Local, policy-gated MCP tools support OpenOCD, pyOCD and STM32CubeProgrammer, with pytest for CI.
      44
      1,138 PyPI
      18
      Apache 2.0

    • McuBuddy

      cunjun
      A
      license
      C
      quality
      A
      maintenance
      MCP server for AI-assisted MCU and embedded firmware debugging. It connects to real hardware via debug probes, inspects CPU/memory/peripherals, manages Keil builds, and provides structured evidence for fault diagnosis.
      19
      20 PyPI
      6
      MIT

    • stm32-stlink-mcp

      phryniszak
      A
      license
      A
      quality
      C
      maintenance
      MCP server for debugging STM32 microcontrollers over ST-LINK using STM32CubeCLT tools (GDB, ST-LINK_gdbserver, STM32_Programmer_CLI) with session management, flashing, breakpoints, memory/register access, and expression evaluation.
      19
      1
      GPL 3.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

    B3.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: discovery (list_serial_ports), session/capture status, log querying, boot listing, crash retrieval, sending, pattern waiting, and meta-capabilities. Overlaps like capture_status vs list_capture_sessions are resolved by descriptions that distinguish current status/selector from historical session lists.

    Naming Consistency5/5

    All tools use snake_case with a consistent verb_noun or verb_phrase pattern (list_*, get_*, query_*, send_*, wait_for_*). No mixed conventions or vague names appear.

    Tool Count5/5

    10 tools is well within the ideal 3–15 range for a focused hardware-logging MCP. Each tool has a clear purpose and earns its place without redundancy.

    Completeness4/5

    Core workflows—discovery, session selection, log querying, boot/crash inspection, and send/wait verification—are covered. Minor gaps exist (no explicit start/stop capture, limited time-range queries, no standalone crash list), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources