Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

Scope MCP

Small Python server that lets an agent set up, measure and screenshot a Keysight or Agilent oscilloscope over Ethernet.

Reviewed by ReviewRamble editors · Updated

Setup docs Open source

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

3.3/5

A tidy, honest bench helper for one Agilent scope, and a starting point to fork rather than a finished tool for any other model.

What is Scope MCP?

Scope MCP, from Netlist Studio, connects an MCP client such as Claude Code to a Keysight or Agilent oscilloscope on your network. It can read the scope's identity, run autoscale, start, stop or arm a single acquisition, set the timebase, set each channel's volts per division, offset, coupling and bandwidth limit, configure an edge trigger, take measurements such as frequency, peak-to-peak and rise time, download waveform samples, set up and read UART serial decode, and return a PNG screenshot of the display.

It is a three-file Python project built on FastMCP and PyVISA, MIT-licensed, with 13 GitHub stars and three commits, the last on 23 February 2026. The README lists exactly one tested instrument: an Agilent MSOX2024A on firmware 02.43.2018020635. There is no package release; you clone it and install the dependencies yourself.

How to install Scope MCP

git clone https://github.com/Netlist-Studio/scope-mcp && pip install fastmcp pyvisa pyvisa-py numpy

Is Scope MCP worth it?

Scope MCP does one narrow job well: it turns a networked oscilloscope into something an agent can read and adjust while you probe a board. The source registers 17 tools, three more than the README's table, covering acquisition control, timebase, channel and trigger setup, 13 automatic measurements, waveform download and UART decode on 2 serial buses. The server's own instructions tell the agent to read the scope's state before changing it, which is the right habit.

What it does to hardware is limited to the scope's settings. Autoscale reconfigures every active channel, the timebase and the trigger; the channel tool changes volts per division, offset, coupling, bandwidth limit and whether a channel is shown; run, stop and single change acquisition. Nothing drives the circuit under test, and the reset command in the code is not exposed as a tool. The cost of a wrong call is a lost scope setup, not a damaged board, but there is no confirmation step, so an agent can undo a careful trigger setup in one request.

The server runs over stdio and opens no network port of its own. It connects out to the scope's LAN interface using the VXI-11 address form TCPIP0::<ip>::inst0::INSTR, with a 10-second timeout, and trusts whatever IP you pass with --host or SCOPE_IP. Waveform downloads default to 1,000 points; the docstring puts the ceiling at about 62,500.

The catch: it was tested on one model. The low-level wrapper calls itself a driver for the MSOX2024A. Other Keysight scopes may accept the same commands, but nothing in the repository shows it. The README's clone instructions also point to a misspelt organisation and a folder that does not exist, and there have been no commits since February.

Our take: for anyone with an MSOX2024A, or a similar Keysight scope and an afternoon to check the SCPI differences, this is a clean base that saves writing the PyVISA plumbing. An unattended rig needs more than it offers: confirmations, a second tested model and a maintainer who is still committing.

Where it earns its place

  • A firmware engineer bringing up a new sensor board

    Check that the UART debug output is clean at 115200 baud

    Ask the agent to set up UART decode on channel 1 and read the frames while the board boots, then compare them with the log the firmware should print. It saves switching between scope menus and the terminal.

  • A hardware hobbyist tuning a PWM motor driver

    Measure frequency, duty cycle and rise time after each code change

    After each flash, the agent runs scope_measure_all on the PWM channel and reports the numbers, plus a screenshot when something looks off. Free to run; it needs the scope on the same network as the computer.

  • An electronics lecturer preparing a lab handout

    Capture reference waveforms and screenshots for students to compare against

    Have the agent set the channel and timebase, download up to about 62,500 samples per channel and save screenshots, then check them against the scope's own display before printing.

Before you commit

Setup
Clone the repository, create a Python virtual environment, pip install fastmcp, pyvisa, pyvisa-py and numpy, run connect.py with the scope's IP to test the link, then add scope_server.py to Claude Code with --host or SCOPE_IP. The README's clone URL and cd step need correcting by hand.
Integrations
Any MCP client that can launch a stdio server; the README shows Claude Code. Uses PyVISA with the pure-Python pyvisa-py backend, so no vendor VISA library is needed.
Data and privacy
Runs locally. Measurements, decoded serial frames, waveform samples and screenshots go to your model provider as tool results. The server opens no port; it connects out to the scope's IP and adds no access control of its own.
Cost at scale
Free under MIT; the only costs are your model usage and the instrument.
Limits
One tested model (MSOX2024A, firmware 02.43.2018020635). Edge and UART triggers only; UART is the only serial protocol decoded. Waveforms default to 1,000 points. No package, no releases and no commits since February 2026.

What’s good

  • 17 tools covering setup, measurement, waveforms and UART decode
  • Opens no network port; stdio only
  • Cannot drive the circuit under test
  • Short, readable source that is easy to adapt

What’s not

  • Tested on one model, the Agilent MSOX2024A
  • README clone path and folder name are wrong
  • No confirmation before autoscale or setting changes
  • No commits since 23 February 2026

Best for

Engineers and makers with an Agilent MSOX2024A, or a similar Keysight scope they are willing to verify, on the LAN who want an agent to take measurements and decode UART during board bring-up.

Scope MCP alternatives

Scope MCP: common questions

Is Scope MCP worth it?
A tidy, honest bench helper for one Agilent scope, and a starting point to fork rather than a finished tool for any other model. We rate it 3.3 out of 5.
How much does Scope MCP cost?
Free and open source (MIT).
What are the downsides of Scope MCP?
Tested on one model, the Agilent MSOX2024A; rEADME clone path and folder name are wrong; no confirmation before autoscale or setting changes; no commits since 23 February 2026.
Who is Scope MCP best for?
Engineers and makers with an Agilent MSOX2024A, or a similar Keysight scope they are willing to verify, on the LAN who want an agent to take measurements and decode UART during board bring-up.
How much does Scope MCP cost for a team or in production?
Free under MIT; the only costs are your model usage and the instrument.
Is Scope MCP safe for company data?
Runs locally. Measurements, decoded serial frames, waveform samples and screenshots go to your model provider as tool results. The server opens no port; it connects out to the scope's IP and adds no access control of its own.
What are the best Scope MCP alternatives?
The closest alternatives we have reviewed are LabMCP and Arduino MCP Server.

Answers checked Nov 16, 2026.