# Rigol DHO824 Oscilloscope

Controls Rigol DHO824 oscilloscopes over VISA to capture channel waveforms, grab display screenshots, and inspect measurements in AI clients.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 6
- Author: aimoda
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/aimoda/rigol-dho824-mcp
- Updated: 2025-11-02
- HTML: https://affpapa.org/en/nevibecode/mcp/rigol-dho824-oscilloscope

## What it 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.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Environment variables: `RIGOL_RESOURCE`, `VISA_TIMEOUT`, `RIGOL_BEEPER_ENABLED`, `RIGOL_TEMP_DIR` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
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-mcp
```
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>

### Codex

**Platform CLI**
```bash
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-mcp
```
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>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "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>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "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>

### Gemini CLI

**Platform CLI**
```bash
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-mcp
```
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>

## When to use it
- 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
- Capture waveform data from channel 1 on my oscilloscope
- Take a screenshot of the oscilloscope display

## Similar
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74569
- [Keploy](https://affpapa.org/en/nevibecode/mcp/keploy.md) — MCP server · ★ 18779
- [SeleniumBase MCP](https://affpapa.org/en/nevibecode/mcp/seleniumbase-mcp.md) — MCP server · ★ 13181
- [mobile-mcp](https://affpapa.org/en/nevibecode/mcp/mobile-mcp.md) — MCP server · ★ 10025
- [e2e](https://affpapa.org/en/nevibecode/mcp/e2e.md) — MCP server · ★ 11962
- [mockserver](https://affpapa.org/en/nevibecode/mcp/mockserver.md) — MCP server · ★ 4999

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md