Overview
Keysight MCP Server for Instrument Control lets you describe what you want in natural language instead of writing SCPI commands or scripts. Any engineer can use it, no SCPI experience required. It connects AI assistants that support the Model Context Protocol (MCP) — including Claude Code, Claude Desktop, and GitHub Copilot — to your Keysight instruments.
For example, you can say "measure the gain of this amplifier from 1 GHz to 6 GHz" instead of writing raw SCPI commands. The server handles everything from command resolution to execution. Built-in protections, tailored to each instrument type, catch unintended or risky commands before they run. You review and approve every command before it reaches your hardware.
How It Works
Keysight MCP Server for Instrument Control adds a natural language layer between you and your hardware. When you describe what you want, the system processes your request through these steps:
- Natural Language Input: You describe what you want to measure or configure.
- Intent Resolution: The AI interprets your request and identifies the instrument operation, subsystem, and parameters it needs.
- IDF-Based Command Generation: The server generates commands only from the instrument's Instrument Definition File (IDF), a structured, instrument-specific knowledge base. It never invents a command.
- Engineer Approval: The server shows you a plain-language preview of every command before it sends anything to the instrument.
- VISA Execution: The server sends approved commands to the instrument over VISA (USB, LAN, or GPIB), and returns the results in plain language.
Key Capabilities
| Capability | Description |
|---|---|
| Instrument Discovery | Automatically detects all connected VISA instruments on the system. |
| NLP-to-SCPI Translation | Converts natural language measurement intent into validated SCPI command sequences. |
| IDF Command Validation | Every SCPI command is sourced from the instrument's IDF. Commands are never invented or assumed. |
| Confidence-Based Resolution | A deterministic scoring pipeline rates command matches as high, medium, or low confidence. When results are ambiguous, they are presented to the engineer for selection rather than guessed. |
| Human-in-the-Loop | Every command sequence requires explicit engineer approval before execution. Nothing reaches hardware without confirmation. |
| Procedure Execution | Runs the server's built-in multi-step procedures, such as S-parameter sweeps, SOLT calibration, peak search, continuous-wave output, power supply setup, and DMM voltage readings, using parameters you supply. |
| Save and Reuse Sequences | You can save an approved SCPI sequence for reuse, to share with your team or run again later. |
| Multi-Instrument Sessions | Multiple instruments can be controlled simultaneously within a single session. |
| Offline Operation | Core functions work without a network connection. IDFs and procedures are stored locally and available offline. An internet connection is only required to check and install Keysight MCP Server for Instrument Control updates. |
| Operation Tracking | Every measurement, command, and result in the session is tracked. The full operation history is available for review, supporting traceability and audit requirements. |
| Error Recovery | Errors appear in the execute_commands response, translated into plain language with suggested fixes. By default, the server checks for errors after every command. It stops the sequence as soon as one command fails, so you know exactly which command caused the problem. You can turn this off and check errors only once, at the end of the sequence. Then the sequence keeps running even if a command fails, and you get the full error list at the end. Use get_all_errors to check for errors manually at any time. |
| Screenshot Capture | Captures the instrument display to a local file on demand. Supports oscilloscopes, signal analyzers, network analyzers, signal generators, and FieldFox handhelds. |
| File Transfer | Lists, uploads, downloads, copies, and moves files on instrument storage. Transfer method is selected automatically based on instrument family. |
| Software Updates | Checks for, downloads, and installs updates to the MCP server without leaving the AI client. Each step requires explicit engineer approval. |
| Mock Mode | Simulates instrument behavior without physical hardware. Useful for development, demos, and automated testing. |
Supported Instrument Classes
Keysight MCP Server for Instrument Control supports the following instrument classes, each with class-specific intent resolution and safety rules:
- Signal Analyzers
- Signal Generators
- Network Analyzers
- Oscilloscopes
- Power Supplies
- Precision and Semiconductor Measurement Instruments
- General-Purpose Test Instruments (frequency counters, waveform generators, switches, BER test solutions)
For the full list of supported families and models, see Supported Instruments.
Supported AI Clients
Keysight MCP Server for Instrument Control works with any AI client that supports the Model Context Protocol (MCP). No client-specific configuration is needed beyond the standard MCP server registration described in Getting Started.