rs3005p-mcp
This MCP server lets AI agents remotely control an RS PRO RS-3005P or RS-6005P programmable DC power supply over USB/RS232 serial.
Connection & Discovery
List available serial ports, connect to a supply (specifying model/baud rate), verify identity via
*IDN?, and disconnect
Voltage & Current Control
Set output voltage (0–30 V / 0–60 V) and current limit (0–5 A) with range and safety validation
Ramp voltage gradually to a target within a configured slew rate limit
Bring the device to its profile's nominal operating point
Monitoring & Measurement
Read live output voltage and current measurements
Get current setpoints, decoded device status (output on/off, CV/CC mode, OCP state), or a full snapshot of all setpoints, measurements, and status
Output & Protection Control
Enable or disable the output terminals
Arm or disarm over-current protection (OCP)
Memory Management
Save current panel settings to one of 5 memory slots and recall them
Safety Profile Management
Operator-defined device profiles set safe envelopes (voltage/current/power ceilings, slew limits); the server rejects any request exceeding the active profile's limits
List available profiles, read the active profile, and switch profiles (widening limits requires explicit confirmation)
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rs3005p-mcp Set voltage to 5V and current to 0.5A, then enable output."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
rs3005p-mcp
An MCP server that lets AI agents control an RS PRO RS-3005P (or RS-6005P) digital programmable DC power supply over its USB / RS232 serial interface.
It implements the documented RS Series Remote Control Syntax V2.0 (KORAD-compatible) and exposes voltage/current control, live measurements, output and over-current-protection switching, and panel-memory save/recall as MCP tools.
Supported hardware
Model | Voltage | Current | Remote interface |
RS-3005P | 0–30 V | 0–5 A | USB + RS232 |
RS-6005P | 0–60 V | 0–5 A | USB + RS232 |
The non-P variants (RS-3005D / RS-6005D) have no remote interface and
cannot be driven by this server.
Serial settings (fixed by the firmware): 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control.
Related MCP server: ScopeMCP
Install
uv venv
uv pip install -e .Run
The server speaks MCP over stdio:
uv run rs3005p-mcpClaude Code / Claude Desktop config
{
"mcpServers": {
"rs3005p": {
"command": "uv",
"args": ["run", "rs3005p-mcp"],
"cwd": "C:/path/to/rs3005p-mcp"
}
}
}Tools
Tool | Purpose |
| Discover the COM/tty port the supply is on. |
| Open the port, pick the model, verify with |
| Close the connection. |
| Read the |
| Read the active safety envelope (read-only). |
| List device profiles in the library + which is active. |
| Switch active profile (widening needs |
| Set the voltage setpoint (range + safety validated). |
| Set the current limit (range + safety validated). |
| Ramp voltage to a target within the slew limit. |
| Bring the DUT to its profile's nominal operating point. |
| Read configured voltage & current setpoints. |
| Read actual output voltage & current. |
| Enable/disable the output terminals. |
| Arm/disarm over-current protection. |
| Decoded status: output, CV/CC mode, OCP. |
| Full snapshot (setpoints + measurements + status). |
| Store panel settings to memory slot 1–5. |
| Recall panel settings from memory slot 1–5. |
Safety profiles (protecting attached devices)
To stop an agent from over-driving the device wired to the terminals, supply a device-profile library at launch. It defines a safe envelope (voltage / current / power ceilings, output gating, slew limit) per device; the server rejects any agent request that would leave it. Profiles are set by the operator at startup and cannot be changed by any tool.
rs3005p-mcp --profile devices.json --device 24v-sensorRS3005P_DEVICE/--device is only the default; an agent can switch among the
curated devices at runtime with select_device (widening the envelope requires
confirm_widen=true) and devices.json edits hot-reload on the next
connect/select_device — no re-registration. No tool can create or modify a
profile's limits; the file stays operator-curated.
See docs/safety.md and
examples/devices.example.json. With no profile
the server runs limited only by hardware (30 V / 5 A) and says so on every
connect.
A typical agent flow:
list_serial_ports→ find the port.connect(port="COM4")→ verifies identity, applies RS-3005P limits.set_voltage(5.0),set_current(0.5).set_output(True).measure()→ live readings.
Development
uv pip install -e ".[dev]"
uv run pytestTests run against an in-memory device emulator (tests/conftest.py), so no
hardware is required. See docs/ for the protocol reference and
architecture notes.
License
MIT.
Available Tools
14 toolsconnectA
Open a serial connection to the power supply and verify it responds.
Args:
port: Serial port name, e.g. COM4 or /dev/ttyUSB0.
model: One of the supported models (sets the voltage/current limits).
Defaults to RS-3005P (0-30 V, 0-5 A).
baudrate: Serial baud rate; the manual specifies 9600.
Returns the device identification string and the active output limits.
Inputs: port (required), model, baudrate.
disconnectA
Close the serial connection to the power supply.
Inputs: no named parameters.
get_identificationA
Return the instrument identification string (*IDN?).
Inputs: no named parameters. Returns: result
get_setpointsA
Return the configured voltage and current setpoints.
Inputs: no named parameters.
get_stateA
Return a full snapshot: setpoints, live measurements and status.
Inputs: no named parameters.
get_statusA
Return decoded device status: output state, CV/CC mode, OCP state.
Inputs: no named parameters.
list_serial_portsA
List serial ports available on this machine.
Use this to find the port the power supply is on (it enumerates as a USB
virtual COM port, e.g. COM4 on Windows or /dev/ttyUSB0 on Linux).
Inputs: no named parameters. Returns: result
measureA
Read the actual output voltage (V) and current (A) at the terminals.
Inputs: no named parameters.
recall_settingsB
Recall panel settings from memory slot (1-5).
Inputs: slot (required).
save_settingsA
Store the current panel settings into memory slot (1-5).
Inputs: slot (required).
set_currentA
Set the output current limit, in amps (0-5 A).
In constant-current operation this is the current the supply holds the output to; rejected if outside the model's range.
Inputs: amps (required).
set_ocpA
Arm (True) or disarm (False) over-current protection.
When armed, the output is cut off if the current reaches the setpoint.
Inputs: enabled (required).
set_outputB
Enable (True) or disable (False) the output terminals.
Enabling makes the terminals live at the configured setpoints.
Inputs: enabled (required).
set_voltageA
Set the output voltage setpoint, in volts.
Rejected if outside the connected model's range (e.g. 0-30 V on RS-3005P).
Inputs: volts (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose: connection management, configuration, measurement, status queries, memory operations, and output control. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (e.g., set_voltage, get_state, list_serial_ports), making them predictable and easy to distinguish.
14 tools cover the essential operations for a programmable power supply without being excessive. Each tool serves a clear purpose, and the count is well-scoped for the domain.
The tool set covers core operations: connection, configuration, measurement, status, memory, and protection. Minor omissions like a factory reset or calibration tool are present but not critical for typical use.
Maintenance
Related MCP Connectors
MCP server for building and testing AI agents with multi-model experimentation and insights.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
Related MCP Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables AI agents to operate an oscilloscope through high-level tools like signal capture and measurement, abstracting vendor-specific SCPI commands.184MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI assistants to the Owon DS1102 oscilloscope, enabling waveform capture, measurement retrieval, and remote control of scope settings.GPL 3.0
- AlicenseAqualityDmaintenanceMCP server for controlling B&K Precision and Manson bench power supplies, enabling voltage/current setting, output switching, and power cycling.83MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for reading and controlling an OWON SPE6103 programmable DC power supply over USB serial, with safety checks and verified SCPI commands.MIT