Skip to main content
Glama
dengtaowei

logic-mcp

by dengtaowei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to logic-mcp

No user-submitted related servers found.

    Related Servers

    • dsview-mcp

      modelclixxo
      F
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for building an agent-facing integration around DreamSourceLab DSView. Enables native logic capture, protocol decode, and analysis with artifact management for I2C, SPI, and UART.
      -

    • mcp-sigrok

      daedalus
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes all functionality of sigrok-cli as MCP tools, enabling hardware initialization, signal acquisition, and protocol decoding for logic analyzers.
      25 PyPI
      2
      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

    • buspirate-mcp

      mplogas
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for BusPirate 6 hardware security testing. Exposes UART, SPI, I2C, 1-Wire, power supply, GPIO, and logic analyzer operations as tools.
      2
      MIT

    • mindustry-mcp

      hubdustrylab
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to launch and manage an owned Mindustry runtime, create logic fixtures, configure processors with mlog programs, observe live memory values, and verify program replacements with digest preconditions.
      6 npm
      1
      -
    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

    C2.9/5.0

    Scored across 19 tools

    Disambiguation3/5

    Most tools map to distinct workflow phases, but instrument_capture vs instrument_start plus wait, and display_analyze vs display_reconstruct, have closely overlapping responsibilities. protocol_list and instrument_list also both touch backends, so an agent could misselect without careful reading.

    Naming Consistency3/5

    The instrument_* family is consistently named and object_verb names like capture_open and bus_decode are readable, but interpret is a bare verb and instrument_capabilities, protocol_roles, and session_status are noun-style rather than action-style. This mixed convention is understandable but not fully predictable.

    Tool Count3/5

    19 tools sits in the 16-25 heavy band, though the logic-analyzer workflow is broad enough to justify many of them. Some consolidation is possible, especially around capture/start and the display sugar tools, without losing core capability.

    Completeness4/5

    The server covers the full capture-to-decode pipeline: discovery, opening instruments, configuration, capture, decode, upper decoding, display reconstruction, and session status. Minor gaps like explicit decode-job teardown or saved artifact handling are present but agents can generally work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources