Skip to main content
Glama
colingimenez

SCPI MCP

by colingimenez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SCPI MCP

No user-submitted related servers found.

    Related Servers

    • instrumentControl

      alwaysmy
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables unified discovery, query, and control of laboratory instruments (power supplies, oscilloscopes, signal generators, multimeters) via VISA/SCPI, with device-specific libraries and an MCP server exposing 19 tools for natural language interaction.
      -

    • Instrument MCP Server

      zeng-andrew
      A
      license
      C
      quality
      B
      maintenance
      Enables natural language control of test instruments like spectrum analyzers and power supplies via SCPI commands, with auto-discovery and multi-instrument session support.
      100
      1
      MIT

    • siglent-scpi-mcp

      mp911de
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to connect to and control Siglent oscilloscopes and power supplies over SCPI/TCP using typed tool calls with input validation, safety controls, and built-in observability.
      Apache 2.0

    • rigol-oscilloscope-mcp

      zinntikumugai
      A
      license
      A
      quality
      A
      maintenance
      Enables LLMs to control RIGOL oscilloscopes over SCPI via LAN or USB, including configuring channels/timebase/trigger, taking measurements, capturing waveforms and screenshots, decoding serial protocols, running FFT analysis, and controlling the built-in AFG.
      38
      MIT

    • pyvisa-mcp

      abhinav937
      A
      license
      A
      quality
      C
      maintenance
      Puts PyVISA in front of AI tools so they can discover and drive oscilloscopes and other SCPI instruments over LAN, USB, GPIB, and serial. Builds a per-instrument local knowledge base from identity, manuals, and past commands, then exposes tools for SCPI queries, measurements, waveform capture and export, and scope configuration.
      22
      MIT

    • instrument-mcp

      mingyo186
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects test and measurement instruments (oscilloscope, logic analyzer, multimeter, power supply) to AI via MCP, enabling natural language control and automated analysis.
      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

    B3.4/5.0

    Scored across 76 tools

    Disambiguation4/5

    Device-specific prefixes (arb_, dmm_, osc_, psu_) cleanly separate tools by instrument, and most tools target a unique parameter. A few pairs like dmm_read vs dmm_measure and psu_get_voltage vs psu_measure_voltage have overlapping semantics, though descriptions clarify the distinction.

    Naming Consistency4/5

    Most tools follow a consistent device_verb_noun pattern (e.g., arb_set_frequency, psu_measure_current), making the set highly predictable. Minor deviations such as osc_screenshot, psu_recall, and arb_get_basic_waveform break the strict pattern but are still understandable.

    Tool Count3/5

    76 tools is a high number, but the server covers four independent instruments with 15-22 tools each, matching the device-specific scope. The count feels heavy for an agent to sort through, though naming conventions and prefix grouping mitigate the burden.

    Completeness4/5

    The surface covers the vast majority of operations needed for the four instruments: waveform generation, DMM measurement and statistics, oscilloscope triggering/measurement, and PSU output/protection. The most notable gap is lack of oscilloscope waveform data acquisition (raw trace points), which agents may need for signal analysis.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources