Control and query Rigol DHO824 oscilloscope for waveform capture and measurements
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
An MCP (Model Context Protocol) server for controlling and querying the Rigol DHO824 oscilloscope.

Built by ai.moda.
This project only supports DHO804/DHO824 oscilloscopes (identical hardware). We recommend purchasing a DHO804.
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.
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.
The recommended way to use this MCP server is via Docker, which eliminates dependency management and provides isolation.
Pull the pre-built image from GitHub Container Registry:
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:
-e RIGOL_RESOURCE="TCPIP0::192.168.1.100::inst0::INSTR"-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).
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/rigol internally and translates paths to this value in responses. Must match the host path in your -v mount. 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.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.
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.
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.
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_DIR in 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:
/tmp/rigol-data in examples) must exist before starting the serverRIGOL_TEMP_DIR must match the host-side path in your -v mountwaveform_capture_<timestamp>/ for waveforms and screenshot_<timestamp>.png for screenshotsExample: Manual cleanup
-i flag (interactive mode)RIGOL_RESOURCE is set correctlyping <ip-address>)-e VARIABLE_NAME in the Docker args arrayenv field of .mcp.jsonTo build the Docker image yourself:
Then use rigol-dho824-mcp:local as the image name in your configuration.
For local development and contributions, you can install the MCP server in a Python virtual environment.
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.100 with your oscilloscope's IP addressNote: Unlike Claude Code, Codex requires explicit environment variables via --env flags (before the server name) as it runs MCP servers in a sanitized environment.
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)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)
TCPIP0::192.168.1.100::inst0::INSTRVISA_TIMEOUT: Communication timeout in milliseconds (default: 5000)For local development and testing, you can run the server directly with Python:
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/rigol-dho824-oscilloscope)<a href="https://allmcps.com/mcp/rigol-dho824-oscilloscope"><img src="https://allmcps.com/api/badge/rigol-dho824-oscilloscope?style=directory" alt="Rigol DHO824 Oscilloscope on AllMCPs" /></a>