Rigol DHO824 Oscilloscope
io.github.aimodaPublished by GitHub account aimodav0.1.143-main.2b177aeUpdated Oct 28, 2026
Control and query Rigol DHO824 oscilloscope for waveform capture and measurements
Overview
Lets an assistant control and query a Rigol DHO824/DHO804 oscilloscope over VISA for waveform capture, screenshots and measurements.
- What you can do
- Capture waveforms from oscilloscope channels and save them to temporary files
- Take screenshots of the instrument display, optionally automatically after each tool call
- Query and control the oscilloscope over a VISA connection, including beeper settings
- Return file paths translated from the container to the host so captures can be opened
- When to use it
- Useful when you have a Rigol DHO804/DHO824 on your network and want an assistant to drive it hands-free: grabbing waveforms, taking screenshots and reading measurements during bench work or debugging.
- Requirements
- Runs locally via Docker (recommended) or a Python package. Needs network access to the instrument and the RIGOL_RESOURCE VISA string (for example a TCPIP address). Docker setups also need RIGOL_TEMP_DIR matching a mounted host directory; optional VISA_TIMEOUT, RIGOL_BEEPER_ENABLED and RIGOL_AUTO_SCREENSHOT. The scope must be flashed to DHO824 firmware 00.01.04.
Installation
In SourceWeft
- Open Rigol DHO824 Oscilloscope in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Rigol DHO824 MCP Server
An MCP (Model Context Protocol) server for controlling and querying the Rigol DHO824 oscilloscope.
[Demo of oscilloscope in action]
Built by ai.moda.
Hardware Requirements
Supported Models
This project only supports DHO804/DHO824 oscilloscopes (identical hardware). We recommend purchasing a DHO804.
Firmware Requirements
IMPORTANT: The DHO804 must be flashed to DHO824 firmware before using this MCP server. Use the rigol_vendor_bin project to flash your oscilloscope.
Supported Firmware Version: 00.01.04
This is the only firmware version we test and support. Other firmware versions may work but are not guaranteed.
Compatibility Note
Other Rigol oscilloscope models may work with this MCP server, but we have no way to test them or guarantee functionality. Use with other models at your own risk.
Installation
The recommended way to use this MCP server is via Docker, which eliminates dependency management and provides isolation.
Quick Start
Pull the pre-built image from GitHub Container Registry:
Using Environment Variables with Docker
IMPORTANT: You must provide the RIGOL_RESOURCE environment variable with your oscilloscope's IP address (e.g., TCPIP0::192.168.1.100::inst0::INSTR).
You can configure the Docker container with environment variables in two ways:
- Hardcoded values (shown in examples below):
-e RIGOL_RESOURCE="TCPIP0::192.168.1.100::inst0::INSTR" - Pass-through from host (recommended):
-e RIGOL_RESOURCE(without=value)
When you use -e VARIABLE_NAME without a value, Docker automatically passes through the variable from your host environment. This is useful if you have environment variables already set in your shell (e.g., in ~/.bashrc or ~/.zshrc).
Environment Variables
RIGOL_RESOURCE: Required - VISA resource string for connecting to the oscilloscope (e.g.,TCPIP0::192.168.1.100::inst0::INSTR)RIGOL_TEMP_DIR: Required for Docker - Host-side path for returned file paths. The container always writes to/tmp/rigolinternally and translates paths to this value in responses. Must match the host path in your-vmount. Outside Docker, this sets the directory for temporary files (waveforms, screenshots); if not set, uses system default temp directory.VISA_TIMEOUT: Communication timeout in milliseconds (default: 30000)RIGOL_BEEPER_ENABLED: Enable/disable oscilloscope beeper sounds (default: false)RIGOL_AUTO_SCREENSHOT: Automatically capture screenshot after each MCP tool execution for visualization/debugging (default: false). Screenshots are saved with human-readable timestamp format (e.g.,auto_screenshot_20251030_143045_123.png) for chronological sorting.
MCP Client Configuration
Claude Code
Option 1: Using .mcp.json file
Create a .mcp.json file in your project directory (or copy from .mcp.json.example):
Option 2: Using CLI
Replace 192.168.1.100 with your oscilloscope's IP address.
Codex
Replace 192.168.1.100 with your oscilloscope's IP address.
Note: After adding the server to your MCP client, restart the client to load the MCP server. The server will translate container paths (/tmp/rigol/*) to host paths (/tmp/rigol-data/*) in all returned file paths.
Your first prompt
Enter the following prompt in your MCP Client to verify your setup:
Your MCP client should connect to the oscilloscope and capture the waveform data.
Accessing Temp Files in Docker
The container writes temporary files (waveform captures, screenshots) to /tmp/rigol internally. To access these files from your host machine:
-
Create a directory on your host for storing temporary files:
-
Mount this directory as a volume and set
RIGOL_TEMP_DIRin your Docker configuration:
The server automatically translates all returned file paths from the container path (/tmp/rigol/*) to the host path (/tmp/rigol-data/*), so you can directly access files at the paths shown in tool responses.
Important notes:
- The host directory (
/tmp/rigol-datain examples) must exist before starting the server RIGOL_TEMP_DIRmust match the host-side path in your-vmount- Temporary files are not automatically cleaned up
- You are responsible for manually cleaning up old waveform and screenshot files
- Files will be organized in subdirectories like
waveform_capture_<timestamp>/for waveforms andscreenshot_<timestamp>.pngfor screenshots
Example: Manual cleanup
Troubleshooting
Container exits immediately
- Ensure you're using the
-iflag (interactive mode) - Verify
RIGOL_RESOURCEis set correctly
Cannot connect to oscilloscope
- Verify oscilloscope IP address and network connectivity (
ping <ip-address>) - Check oscilloscope's remote control settings are enabled
Environment variables not working
- Ensure you're using
-e VARIABLE_NAMEin the Docker args array - Set the actual values in the
envfield of.mcp.json
Building Locally
To build the Docker image yourself:
Then use rigol-dho824-mcp:local as the image name in your configuration.
Development Setup
For local development and contributions, you can install the MCP server in a Python virtual environment.
Create and activate virtual environment
Install the package
Add to MCP Client
After completing the setup steps above, add the local development MCP server to your MCP client:
Claude Code:
Codex CLI:
Replace:
<path-to-this-repo>with the actual path to this repository192.168.1.100with your oscilloscope's IP address
Note: Unlike Claude Code, Codex requires explicit environment variables via --env flags (before the server name) as it runs MCP servers in a sanitized environment.
Development Scripts
The scripts/ directory contains utilities for development:
convert_png_to_webp.sh- Convert PNG frame sequences to animated WebP (e.g.,./scripts/convert_png_to_webp.sh "~/screenshots/*.png" output.webp)
Development Configuration
The server can be configured using environment variables. Create a .env file from the example:
Then edit .env to set your configuration:
RIGOL_RESOURCE: VISA resource string for the oscilloscope (required)- Example:
TCPIP0::192.168.1.100::inst0::INSTR
- Example:
VISA_TIMEOUT: Communication timeout in milliseconds (default: 5000)
Running the Server (Development)
For local development and testing, you can run the server directly with Python:
STDIO Transport
HTTP Transport
Source: README.md at commit 2b177ae
Tools
0Version history
1- v0.1.143-main.2b177aeLatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts