Skip to main content
Glama
wolog1

siglent-sds-mcp

by wolog1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to siglent-sds-mcp

No user-submitted related servers found.

    Related Servers

    • oscilloscope-mcp

      lxkang00
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote control of Siglent oscilloscopes via SCPI over TCP/IP, allowing natural language commands for configuration, measurements, and waveform data retrieval.
      -

    • 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

    • 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.
      2
      MIT

    • niscope-mcp

      YMZDS
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to directly control NI oscilloscopes (e.g., PXIe-5160/5164/5110) through the Model Context Protocol, including waveform acquisition, measurement, and configuration.
      MIT

    • 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
      11 npm
      7
      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

    C2.7/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes, but there is some overlap between auto_setup_tcp and auto_find_waveform_tcp, and between the two UART capture tools. However, detailed descriptions help differentiate them, so confusion is limited.

    Naming Consistency3/5

    The '_tcp' suffix is consistently used for oscilloscope communication tools, but naming patterns vary (e.g., modbus_rtu_timing and project_status are noun-first, while others are verb-first). This mixed style is readable but not fully predictable.

    Tool Count3/5

    With 20 tools, the set is at the heavy end for a specialized server, but each tool serves a specific function. Some tools like capture_uart_2mbps_tcp and auto_find_waveform_tcp feel niche or redundant, suggesting the count could be slightly trimmed.

    Completeness4/5

    Core oscilloscope operations (connect, configure, measure, capture, screenshot) are well covered, and there are dedicated analysis tools for UART, RS485, and Modbus. However, there is no explicit RS485 capture tool, and some operations like separate trigger configuration are bundled into broader tools, leaving minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources