Skip to main content
Glama
zinntikumugai

rigol-oscilloscope-mcp

by zinntikumugai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to rigol-oscilloscope-mcp

No user-submitted related servers found.

    Related Servers

    • Rigol DHO824 MCP Server

      aimoda
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables control and querying of Rigol DHO824 oscilloscopes, allowing users to capture waveforms, take screenshots, and interact with oscilloscope settings through natural language.
      5
      MIT

    • claudiscope

      w1nston269
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude or users to control SCPI-compatible oscilloscopes over Ethernet or USB, including measuring signals, changing settings, sending queries/writes, and capturing screenshots.
      MIT

    • pyMSO5000 MCP Server

      mabl
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control Rigol MSO5000 oscilloscopes through VISA, including acquisition, channels, trigger, timebase, waveform generator, display, and front-panel controls, with risk-based permission gating for direct SCPI operations.
      3
      MIT

    • rigol

      sparkybrit
      F
      license
      A
      quality
      C
      maintenance
      Enables Claude Code sessions to control a Rigol DS1054Z oscilloscope over USB, reading identity, settings, measurements, screenshots and waveforms, and applying undoable or destructive changes such as channel, timebase, trigger and acquisition configuration, run control, autoscale and reset. Tool calls come with read-only and destructive hints so safe operations can be auto-approved while risky ones stay behind user approval.
      17
      -

    • PicoScope MCP Server

      markuskreitzer
      F
      license
      A
      quality
      D
      maintenance
      Enables LLMs like Claude to interact with PicoScope oscilloscopes for signal acquisition, measurement, and analysis. Supports device management, data capture, triggering, and signal generation through natural language commands.
      24
      6
      -

    • pico-mcp

      Schimmilab
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to control a PicoScope 5000A USB oscilloscope for signal generation, block capture, measurements, and frequency response sweeps.
      1
      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.8/5.0

    Scored across 38 tools

    Disambiguation4/5

    Tools are mostly organized by subsystem with clear configure_*/get_* pairing, so a careful agent can usually tell them apart. The main overlaps are trigger status between get_trigger and get_acquisition_state, and summary statistics between measure and analyze_waveform, but the detailed descriptions resolve most ambiguity.

    Naming Consistency3/5

    The dominant configure_*/get_* pattern is consistent and readable, but it is broken by bare verbs like run, stop, single, autoset, and measure, plus odd forms like scope_identify and sync_afg_phase. The convention is recognizable but not applied uniformly enough for a 5.

    Tool Count3/5

    38 tools is a heavy surface, but the scope is genuinely broad: connection, acquisition, measurement, waveform capture, math, decode, AFG, cursors, meters, histograms, and references. The count is defensible because each tool maps to a distinct device function, though it is near the upper limit of what an agent can comfortably navigate.

    Completeness4/5

    The set gives thorough lifecycle coverage: connect/identify, acquire/control, configure and read the main axes, measure and capture waveforms, plus deep subsystems like math, decode, AFG, cursors, meters, histograms, and references. Minor gaps exist—no explicit acquisition-mode/memory-depth configuration and no digital-channel enable/threshold control—but core workflows have no dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources