msox2014a-mcp
Related Servers
Alternatives to msox2014a-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.38MIT
- AlicenseAqualityCmaintenancePuts 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.221MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables 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.6MIT
- AlicenseBqualityDmaintenanceEnables agentic coding harnesses to control benchtop test equipment — waveform generator, multimeter, oscilloscope, and power supply — over SCPI, with typed tools and raw passthrough for investigating circuits.761MIT
- AlicenseNot gradedqualityBmaintenanceExposes 16 read-write tools over Stdio or HTTP JSON-RPC that let AI agents stream and inspect oscilloscope waveforms, configure channels and derived math formulas, manage plots and layout, run step-response, FFT/THD and filter analysis, capture screenshots, and navigate the workbench. Runs headlessly against captured data or in live sync with the running desktop app.MIT
TDQS
Scored across 8 tools
Each tool maps to a distinct stage of scope work (connect, configure, trigger, capture, measure, wavegen), so an agent can generally pick correctly. The main soft spots are scope_measure vs scope_capture (both produce signal data) and scope_scpi, which can theoretically do anything the other tools do.
All eight tools use a uniform scope_<noun/verb> snake_case pattern with no deviations. The prefix also correctly identifies the server's instrument domain.
Eight tools is well within the sweet spot and each covers a coherent functional area: session, configuration, trigger, acquisition, measurement, wavegen, raw SCPI, help. No tool feels redundant or padded.
The core lifecycle — discover/connect, configure, trigger, capture, measure, generate — is fully covered, plus a raw SCPI escape hatch and help. Secondary areas like math/FFT setup, cursors, serial decode, or save/recall of instrument setups are absent, though SCPI can bridge them.