Skip to main content
Glama
armchairdeity

scpi-mcp

by armchairdeity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to scpi-mcp

No user-submitted related servers found.

    Related Servers

    • ScopeMCP

      Kletternaut
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects AI assistants to the Owon DS1102 oscilloscope, enabling waveform capture, measurement retrieval, and remote control of scope settings.
      GPL 3.0

    • siglent-sds-mcp

      MagnusJohansson
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to control Siglent SDS oscilloscopes over a local network using SCPI commands. It allows users to measure signals, configure channel and acquisition settings, and capture waveforms or screenshots through natural language.
      13
      5 npm
      7
      MIT

    • SkippyMCP

      krystalmonolith
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for controlling Rigol oscilloscopes from an AI assistant. It translates MCP tool calls into SCPI commands over PyVISA.
      1
      MIT

    • keyscope-mcp

      AnterCreeper
      A
      license
      Not graded
      quality
      D
      maintenance
      AI-native oscilloscope control. A pure-Python MCP service that lets LLM agents control Keysight EDUX1052G oscilloscopes via a compact DSL.
      MIT

    • rigol-mcp

      erebusnz
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for controlling Rigol DS1000Z series oscilloscopes over LAN using natural language. It enables users to take measurements, configure instrument settings, and capture screenshots directly through an MCP client.
      17
      28
      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.9/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct oscilloscope operation. Acquisition, capture, measurement, and configuration tools have clear, non-overlapping purposes. Even similar tools like acq_run and acq_single are differentiated by continuous vs single-shot acquisition.

    Naming Consistency4/5

    Tools predominantly follow a consistent verb_noun pattern (e.g., set_channel, capture_screen). Minor deviations like 'identify' and 'self_config' slightly break the pattern but remain intuitive. Overall, naming is predictable and readable.

    Tool Count5/5

    18 tools comprehensively cover essential oscilloscope operations without redundancy. The count is well-scoped for a domain-specific server, providing enough granularity for complex workflows while remaining manageable.

    Completeness4/5

    Core lifecycle tasks (connect, configure, acquire, capture, measure) are fully covered. Advanced features like FFT or automated calibration are absent but not critical for basic SCPI control. Minor gaps exist but do not hinder primary use cases.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources