OWON MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
OWON MCP
A local stdio MCP server for OWON oscilloscopes. Connect an MCP client to read settings, capture waveforms, query measurements and the multimeter, export data, and optionally control acquisition or record a sequence of screen traces.
USB transport, protocol detection and waveform decoding come from
OWON Scope Web, pinned to a source
revision in pyproject.toml and uv.lock. This project adds MCP tools, explicit
USB ownership, response limits, recording and an HDS200 control adapter.
Hardware validation: HDS2102S, firmware V4.7.1, on macOS / Apple Silicon. Other OWON models use upstream drivers and have not been validated here. See hardware support and troubleshooting for the tested controls and protocol caveats.
Install from source
Requires Python 3.11+, Git, uv, and libusb for real hardware. This repository is the installation source; the instructions do not depend on a PyPI release.
git clone https://github.com/darekxan/owon-mcp.git
cd owon-mcp
# macOS hardware access:
brew install libusb
uv sync --locked
uv run --no-sync owon-mcp --versionOn Linux, install libusb-1.0 and configure permissions using the upstream USB setup instructions. On Windows, follow the upstream WinUSB driver instructions. The offline demo and test suite do not require a scope or libusb. Hardware compatibility on Linux and Windows is not established by the offline tests.
Related MCP server: ScopeMCP
Configure an MCP client
Use the installed executable as a local stdio server. Copy
examples/mcp.json into a client that accepts mcpServers
configuration, replacing both paths with your checkout location:
{
"mcpServers": {
"owon": {
"command": "/absolute/path/to/owon-mcp/.venv/bin/owon-mcp",
"args": ["--export-dir", "/absolute/path/to/owon-mcp/exports"]
}
}
}On Windows, the executable is .venv/Scripts/owon-mcp.exe; use forward slashes or
JSON-escaped backslashes in paths. An absolute executable path avoids dependence
on a GUI client's shell environment. Restart the configured server after changes.
For Codex, examples/codex.toml provides the equivalent
mcp_servers.owon entry. For a project-local configuration, copy it to
.codex/config.toml and replace its paths. The local configuration is ignored by
Git. The optional hardware control scripts also read this file.
The default profile disables instrument setting and acquisition writes. It still
allows explicit USB discovery/connection, queries, and local capture exports.
Add --allow-control to args to enable controls and recording. There are no
unrestricted SCPI writes, USB-reset, firmware-flashing or function-generator tools.
The MCP server does not open a network port. Protocol output goes to stdout and logs to stderr. Starting it, initializing MCP, listing tools and reading status do not scan or open USB. There are no automatic connections or background scans.
First capture
Release the scope in OWON Scope Web or any other USB application. Only one process can claim its interface at a time.
Put the instrument in HID/control mode instead of MSC storage mode.
Call
owon_discoverto list candidates without probing their protocol.Call
owon_connect. Supply a discovereddevice_idif several scopes exist.Call
owon_get_settings, thenowon_capturewith, for example:{"max_points": 300, "include_samples": true, "include_raw": false}Optionally call
owon_export_capturewith{"format": "json"}or{"format": "csv"}. Export before disconnecting: disconnect clears the cached capture.Call
owon_disconnectto release USB. Normal server shutdown also disconnects.
You can ask a client: “Discover my OWON scope, connect, read its settings, capture both enabled channels, export the full capture as JSON, then disconnect.” Discovery and connection happen only when those tools are explicitly called.
Tools
Tool | Purpose |
| Cached connection, demo, control and recording state |
| List USB candidates without protocol probing |
| Claim and identify / release one instrument |
| Cached driver capabilities and accepted control values |
| Read channels, timebase, trigger and acquisition state |
| Capture enabled traces and statistics, with optional samples/raw data |
| Query multimeter values without changing its mode |
| Query instrument-calculated extrema, amplitude, period or frequency |
| Typed setting/acquisition writes; requires |
| Start bounded background recording; requires |
| Check progress / request stop and cleanup |
| Read cached upstream diagnostics |
| Write a full cached capture as JSON or CSV |
Resources owon://status and owon://capture/latest expose cached status and a
capture summary. See tool reference for arguments, limits, control
values, cache lifetime and data semantics.
Recording
After explicitly connecting, set the channels, probe ratios and timebase, then call
owon_record_start:
{"duration_s": 60, "interval_s": 0.2, "filename": "sequence.json"}It selects AUTO sweep and RUN, saves full traces and raw diagnostics under
--export-dir, and returns immediately. Poll owon_record_status or call
owon_record_stop. Recordings are limited to 600 seconds, intervals of 0.05–5
seconds, and 10,000 scheduled frames. Slow USB reads can reduce the achieved rate.
Recording changes the instrument state: cleanup attempts STOP and disconnect
on completion, manual stop or failure. It does not restore the previous sweep or
run state. Reconnect before further scope work. A stopping result means cleanup
is still pending; inspect the terminal status and any error/cleanup_errors.
Only status and recording stop are available while recording is active.
Limits that matter when interpreting data
A capture is a sequence of header/channel reads during acquisition, not an atomic hardware snapshot. Recordings have gaps and do not extend ADC memory.
Voltage scaling, probe metadata and point spacing come from the pinned upstream decoder. Screen-point spacing is not necessarily the acquisition sample period.
max_pointsdecimates each returned trace; it is not a peak-preserving filter. Full samples stay cached for export.include_raw=trueattaches full diagnostics, which are outside the sample limit and can produce large responses.Bare numeric DMM replies have
unit=null; units and overload text are never inferred. Activate DMM mode on the instrument when needed.Most controls confirm command dispatch only. HDS200 sweep/Single readback is checked; use settings readback to assess other controls. Native position offsets are not advertised as calibrated divisions.
Automatic USB reset recovery is disabled. A timeout is reported to the client; manual reconnection may be necessary.
Try it without hardware
Add --demo to the MCP client's server arguments to use simulated traces, settings,
DMM values and measurements. Discovery and connection remain explicit, and status
and captures identify the simulation. Add --allow-control for simulated writes.
Running the executable directly starts stdio MCP and waits for a client:
uv run --no-sync owon-mcp --demoDevelopment and checks
uv sync --locked
uv run --no-sync pytest -q
uv run --no-sync ruff check .
uv buildTests use synthetic drivers, replay data and real MCP clients, including a stdio subprocess. They do not access hardware. GitHub Actions runs the offline checks and builds across the configured Python/platform matrix.
For an explicit hardware read check, disconnect other USB clients, then run:
uv run --no-sync python scripts/live_smoke.pyIt connects, reads settings/capture, exports and disconnects, without scope control
writes. Add --dmm only when DMM mode is ready. Control and trigger checks are
documented separately in hardware support; they change settings.
Local recordings, captures, firmware and client configuration are excluded from the repository and package archives.
CLI options
Option | Default / meaning |
| Use a USB-free simulated instrument |
| Enable setting/acquisition writes and recording |
| Output directory; defaults to |
| Send diagnostic logs to stderr |
| Print usage/version without loading the USB backend |
License and upstream
MIT; see LICENSE. OWON Scope Web is MIT-licensed by Francisco Mesas
Cervilla; see NOTICE. The upstream revision is
cb86012000048b8441318a293fe7a41a83f98023. This project is independently developed
and is not affiliated with OWON. Firmware is not included.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Workflow diagnostics, capability routing, and x402 settlement for MCP-compatible agents.
An authenticated remote MCP server for user-owned devices and one-shot capability invocation.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Remote MCP utilities for agents: structured data, commerce checks, and x402 paid API discovery.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for controlling Hantek DSO2D15 and other DSO2000-family oscilloscopes via USB and SCPI, enabling waveform acquisition, measurements, and screen captures.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI assistants to the Owon DS1102 oscilloscope, enabling waveform capture, measurement retrieval, and remote control of scope settings.GPL 3.0
- AlicenseAqualityBmaintenanceEnables MCP clients to discover tools, configure a Rigol oscilloscope over LAN, take measurements, and retrieve waveform captures via a containerized stdio server.21MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI clients to operate a RIGOL MHO98 oscilloscope over USB, including configuration, waveform and measurement acquisition, FFT analysis, and protocol decoding.16MIT