Skip to main content
Glama
sandraschi

logic-analyzer-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to logic-analyzer-mcp

No user-submitted related servers found.

    Related Servers

    • dl32

      apiwat59
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to capture, measure, and decode USB logic-analyzer signals, including 16-channel streaming and sigrok protocol decoding for UART, I2C, SPI, CAN, and other protocols.
      MIT

    • oscilloscope-mcp

      sandraschi
      A
      license
      A
      quality
      B
      maintenance
      AI-driven USB oscilloscope control via FastMCP, enabling waveform capture, CSV export, and frequency measurements on PicoScope, Hantek, or a built-in simulator.
      6
      5
      MIT

    • ATK-Logic-MCP

      hugelzhang
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to capture digital waveforms from an ALIENTEK USB logic analyzer, run 208 sigrok protocol decoders with stacked chains (like I2C→SSD1306 or UART→Modbus), and analyze or write .atkdl waveform archives offline without the device attached.
      1
      MIT

    • sigrok-mcp-server

      KenosInc
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to capture, decode, and analyze signals from logic analyzers and measurement devices via sigrok-cli, supporting I2C, SPI, UART, CAN, and 100+ protocols.
      12
      MIT
    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

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the logic-analyzer workflow: device management, configuration, triggering, capture, decoding, and help. la_configure (channels/sample rate) and la_trigger (trigger patterns) could superficially overlap as 'configuration', but their descriptions clearly separate the concerns.

    Naming Consistency5/5

    All six tools use a uniform la_ prefix followed by a single verb-like noun in snake_case (la_help, la_capture, la_configure, la_decode, la_device, la_trigger). The pattern is predictable with no mixing of conventions.

    Tool Count5/5

    Six consolidated tools each covering a clear responsibility is well-scoped for a logic-analyzer server. Sub-operations are pushed into the operation parameter rather than expanding the tool count, keeping the surface tight.

    Completeness4/5

    The surface covers the full lifecycle: device discovery/connect, channel and rate configuration, trigger setup, capture with export (VCD), and sigrok decoding. Minor gaps exist (e.g., continuous/streaming capture or session save/load), but core workflows are complete with no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources