Skip to main content
Glama
RoadToSea

uart-mcp

by RoadToSea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to uart-mcp

No user-submitted related servers found.

    Related Servers

    • Embedded Debug MCP

      bitshelf
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides serial debugging for embedded Linux targets, enabling boot log capture, automatic login, crash detection, U-Boot interrupt, and hardware reset via MCP protocol.
      -
    • sbl-probe by soundbytelabs

      sbl-probeofficial

      soundbytelabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Serial communication and protocol analysis MCP server that gives AI coding assistants direct access to serial ports for reading, writing, decoding, and capturing embedded device output.
      MIT

    • coserial

      FlipFlopszzz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables humans and AI agents to collaboratively control serial ports via MCP tools or Web UI, with real-time data sharing across all participants.
      MIT

    • serial-bridge-mcp

      tt33415366
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables sharing two serial consoles between a local operator and MCP agents, allowing command execution and status monitoring on connected devices.
      -

    • OpenBaud

      Leonezz
      A
      license
      Not graded
      quality
      A
      maintenance
      Local serial and USB hardware access for coding agents, with typed YAML protocol commands, checksum validation, audited writes, lossless captures, hardware-free replay, and MCP App visualizations. Runs locally over stdio; live hardware use requires a serial device connected to the same machine.
      6
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation4/5

    Each tool has a clearly distinct role—port discovery, capture session management, read variants, write/send/query variants, and offline parsing—so agents can generally select the right tool. The main ambiguity is between serial_write and serial_send, and between serial_read and serial_get_recent, though their descriptions do clarify the intended use cases.

    Naming Consistency4/5

    The vast majority of tools follow a serial_<verb> snake_case pattern, which is predictable and easy to scan. However, list_ports and protocol_parse break the serial_ prefix convention, and serial_status and serial_shell are noun-style rather than verb-style, creating minor inconsistencies.

    Tool Count4/5

    Fifteen tools sits at the upper edge of the well-scoped range and mostly earns its place for a comprehensive UART toolkit. The one-shot variants (serial_send, serial_query, serial_shell) and protocol_parse add specialized capability but make the set feel slightly denser than a minimal capture-focused server.

    Completeness5/5

    The tool surface is very complete for UART debugging: it covers port enumeration, capture session lifecycle, continuous reading, writing, event waiting, history search, log paging, buffer reset, and protocol parsing. There are no obvious dead ends or missing core operations for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources