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 "Install 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-mcpSet 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: mcp-rs485
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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Gigaclank/RS3005P-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server