ToolBB-0100Curator pick

oscilloscope-mcp: an agent sets up a Rigol DS1104Z and checks hardware against RTL simulation

oscilloscope-mcp connects Claude Code, Cursor or a custom agent to a Rigol DS1000Z oscilloscope over LAN SCPI. A profile lists the series' 15 trigger types and about 95 parameters, and the server checks requests against it before sending. A compare tool diffs captured edges against an RTL simulation. The README shows an agent-configured four-channel capture on a DS1104Z.

Open original source github.com · Masahiro

Shown working
Why this evidence label?

README screenshot of an agent-configured four-channel capture on a Rigol DS1104Z measuring Raspberry Pi 4 GPIO outputs at 50 to 500 Hz.

How we check entries
Preview image for oscilloscope-mcp: an agent sets up a Rigol DS1104Z and checks hardware against RTL simulation
The source's own preview image, from github.com.

Briefing

The profile comes from Rigol's programming guide. The agent can ask it what is settable, and impossible settings come back rejected with caveats. The scope_compare tool takes a reference edge list, such as one from an RTL simulation, and returns matched, shifted, missing and added edges within a default 50 ns tolerance. Results arrive as measurements, PNG screenshots or a self-contained HTML waveform viewer.

Only the DS1104Z has been tested on hardware. The README lists what is still unconfirmed there, including non-edge trigger parameters and a real simulation-versus-hardware comparison. The capture shows Raspberry Pi 4 GPIO pins driven at 50 to 500 Hz. A raw SCPI tool bypasses the profile checks.

From the GitHub API

Repository facts

Repository facts for masahiro-999/oscilloscope-mcp, from the GitHub API
Repositorymasahiro-999/oscilloscope-mcp
Stars3
LicenseMIT Permissive
LanguagePython
Last push28 Jun 2026 4 mo ago

Tags

Instrument

Report a problem with this entry