Rigol DHO824 Oscilloscope — Claude Code MCP server: install & setup
Controls Rigol DHO824 oscilloscopes over VISA to capture channel waveforms, grab display screenshots, and inspect measurements in AI clients.
claude mcp add --env RIGOL_RESOURCE=<RIGOL_RESOURCE> --env VISA_TIMEOUT=<VISA_TIMEOUT> --env RIGOL_BEEPER_ENABLED=<RIGOL_BEEPER_ENABLED> --env RIGOL_TEMP_DIR=<RIGOL_TEMP_DIR> --transport stdio rigol-dho824-oscilloscope -- uvx rigol-dho824-mcpWhat Rigol DHO824 Oscilloscope does
This server connects your development assistant to a Rigol DHO824 or converted DHO804 scope across the local network. It processes tool calls and communicates with hardware over TCP/IP using the VISA protocol.
Hardware support centers strictly on firmware version 00.01.04. If you run a DHO804, flash it to DHO824 firmware beforehand via rigol_vendor_bin. When deploying via Docker, map an existing host folder to /tmp/rigol and assign its location to RIGOL_TEMP_DIR. The server keeps generated waveform folders and PNGs on disk without automatic cleanup.
What it helps with
- pull waveform traces from active oscilloscope channels
- save oscilloscope display screenshots during test runs
- inspect hardware measurements directly inside an AI session
- automate capture runs during circuit debugging
Example prompts for the agent
- Capture waveform data from channel 1 on my oscilloscope
- Take a screenshot of the oscilloscope display
How to install Rigol DHO824 Oscilloscope
Platform CLI
claude mcp add --env RIGOL_RESOURCE=<RIGOL_RESOURCE> --env VISA_TIMEOUT=<VISA_TIMEOUT> --env RIGOL_BEEPER_ENABLED=<RIGOL_BEEPER_ENABLED> --env RIGOL_TEMP_DIR=<RIGOL_TEMP_DIR> --transport stdio rigol-dho824-oscilloscope -- uvx rigol-dho824-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from rigol-dho824-mcp <command>
Platform CLI
codex mcp add rigol-dho824-oscilloscope --env RIGOL_RESOURCE=<RIGOL_RESOURCE> --env VISA_TIMEOUT=<VISA_TIMEOUT> --env RIGOL_BEEPER_ENABLED=<RIGOL_BEEPER_ENABLED> --env RIGOL_TEMP_DIR=<RIGOL_TEMP_DIR> -- uvx rigol-dho824-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from rigol-dho824-mcp <command>
Config file
{
"mcpServers": {
"rigol-dho824-oscilloscope": {
"command": "uvx",
"args": [
"rigol-dho824-mcp"
],
"env": {
"RIGOL_RESOURCE": "<RIGOL_RESOURCE>",
"VISA_TIMEOUT": "<VISA_TIMEOUT>",
"RIGOL_BEEPER_ENABLED": "<RIGOL_BEEPER_ENABLED>",
"RIGOL_TEMP_DIR": "<RIGOL_TEMP_DIR>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from rigol-dho824-mcp <command>
Config file
{
"servers": {
"rigol-dho824-oscilloscope": {
"type": "stdio",
"command": "uvx",
"args": [
"rigol-dho824-mcp"
],
"env": {
"RIGOL_RESOURCE": "<RIGOL_RESOURCE>",
"VISA_TIMEOUT": "<VISA_TIMEOUT>",
"RIGOL_BEEPER_ENABLED": "<RIGOL_BEEPER_ENABLED>",
"RIGOL_TEMP_DIR": "<RIGOL_TEMP_DIR>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from rigol-dho824-mcp <command>
Platform CLI
gemini mcp add -e RIGOL_RESOURCE=<RIGOL_RESOURCE> -e VISA_TIMEOUT=<VISA_TIMEOUT> -e RIGOL_BEEPER_ENABLED=<RIGOL_BEEPER_ENABLED> -e RIGOL_TEMP_DIR=<RIGOL_TEMP_DIR> rigol-dho824-oscilloscope uvx rigol-dho824-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from rigol-dho824-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Rigol DHO824 Oscilloscope
How to install Rigol DHO824 Oscilloscope in Claude Code?
Run claude mcp add rigol-dho824-mcp -e RIGOL_RESOURCE=<RIGOL_RESOURCE> -- uvx rigol-dho824-mcp replacing <RIGOL_RESOURCE> with your instrument's VISA resource address.
Which oscilloscope hardware works with this server?
It targets Rigol DHO824 and DHO804 units on firmware version 00.01.04. DHO804 units require flashing to DHO824 firmware using rigol_vendor_bin prior to connection.
Where does the server store captured screenshots and waveforms?
Inside Docker, files land in /tmp/rigol, which must match the host folder mounted and defined by RIGOL_TEMP_DIR.
