Open source · Apache-2.0 · 0.1.0-beta.7
Connect AI assistants to your PLCs, meters and OPC UA servers
Proxus Industrial MCP Server gives Claude, Cursor, VS Code and any other MCP client read-only access to the devices you list: Modbus TCP and OPC UA, with OPC UA security and certificates. 60+ open register maps are built in, so the assistant reads a meter's voltage by name instead of guessing addresses. Ask what a machine is doing, why a value looks wrong or why a device does not answer, and it reads the plant to find out.
- Windows, macOS, Linux and Docker
- One binary, no runtime to install
- Read-only by design
- Listed in the official MCP Registry
read_named(device: "sdm630-1", keys: ["voltage_l1_n", "current_l1", "frequency", "active_power_l1"])
Tools
What the assistant can do
Each tool answers a question engineers ask on the floor. Results come back with units, quality and timestamps, so the assistant can say how sure it is.
- list_devices
- The devices this server may reach, with their ISA-95 path and whether a connection is open.
- read_nodes · browse
- Browse an OPC UA server and read up to 50 variables with quality, status code and source timestamp.
- read_address · decode_registers
- Read Modbus registers and bits, and show every byte and word order side by side when a value looks wrong.
- watch_nodes · watch_address
- Watch values for up to a minute: an OPC UA subscription or Modbus polling, with min, max, average and every change.
- diagnose_connection
- Walk name, TCP, protocol, certificates, login and a test read, and name the layer that fails with the next thing to try.
- find_device_map · get_device_map
- Find the register map for a model or alias such as PM5560, and look up its registers by word: address, type, byte order, unit and scale.
- read_named
- Read registers by key, such as voltage_l1_n or active_energy_import, and get engineering values with units; the map supplies type, byte order and scale.
- verify_device_map
- Check a map against the real device, read-only, and prepare a hardware verification report for the open collection.
Setup
Running in five minutes
- Download Get the archive for Windows, macOS or Linux from the releases page, or use the Docker image.
- List your devices Write the devices the assistant may reach in proxus-mcp.json, with a register map for Modbus devices that have one. Nothing outside that file is reachable.
- Add it to your MCP client Point Claude Desktop, Cursor or VS Code at the binary and the configuration file, then restart the client.
proxus-mcp.json
{
"devices": {
"energy-meter-1": {
"protocol": "modbus-tcp",
"host": "192.168.10.40",
"unit_id": 1,
"map": "schneider-electric/pm5500-pm5600-pm5700"
},
"press-3": {
"protocol": "opc-ua",
"endpoint": "opc.tcp://192.168.10.21:4840",
"security_mode": "sign_and_encrypt",
"security_policy": "Basic256Sha256"
}
}
} Claude Desktop: claude_desktop_config.json
{
"mcpServers": {
"proxus": {
"command": "/path/to/proxus-mcp",
"args": ["--config", "/path/to/proxus-mcp.json"]
}
}
} Register maps built in
Read meters and drives by name
The server ships with the open Modbus Register Maps collection: 60+ energy meters, power analysers, drives and inverters, 20,545 registers, each with its vendor document. Set a device's map in the configuration and the assistant calls read_named instead of decoding raw registers.
- Schneider Electric PM5500/PM5600/PM5700
- Eastron SDM630-Modbus
- Siemens PAC3200
- Schneider Electric ATV320
- Fronius Primo GEN24/Symo GEN24
- ABB B23/B24
Verify a map on your device: verify_device_map reads every register once, checks the values and prepares a report you submit to the collection.
Built for the plant floor
Safe to point at production
- Read-only: no tool writes values, starts or stops a machine, or changes a controller. Register maps say how to read a register, never how to write one.
- Only the devices in the configuration file are reachable; the assistant cannot scan the network.
- OPC UA Basic256Sha256, Aes128_Sha256_RsaOaep and Aes256_Sha256_RsaPss with Sign or SignAndEncrypt; certificates are never trusted automatically.
- Passwords come from environment variables, never from the configuration file.
- Text read from devices is returned as data, so a tag value cannot steer the assistant.
From one engineer to the whole plant
When one MCP server is not enough
The MCP server talks to devices one session at a time. Proxus runs the same idea across the plant: every signal collected once, history kept, a Unified Namespace for all sites, Siemens S7, EtherNet/IP, CNC and more protocols, and the AI Assistant and MCP access with users, roles and an audit trail.
- History and trends, not only what a device reports now.
- More protocols: Siemens S7, EtherNet/IP, Fanuc, Heidenhain and others.
- Users, roles and an audit trail for every AI request.
Questions
MCP server questions, answered.
- What is an MCP server?
- MCP (Model Context Protocol) is an open standard that lets AI assistants call tools. An MCP server offers those tools; here they read industrial devices. Claude Desktop, Cursor, VS Code and other MCP clients start the server and let the model decide when to call each tool.
- Can the assistant change values on my PLC?
- No. Every tool in this release only reads. There is no tool that writes a value, starts or stops a machine, or changes a controller program, and only the devices in the configuration file can be reached.
- Which protocols does it support?
- Modbus TCP and OPC UA. Modbus RTU devices are reached through a Modbus TCP gateway. OPC UA works unsecured or with Basic256Sha256, Aes128_Sha256_RsaOaep and Aes256_Sha256_RsaPss, Sign or SignAndEncrypt, with anonymous or user-name login. Siemens S7, EtherNet/IP and CNC controls are available in the Proxus platform.
- Which devices have a register map?
- Energy meters, power analysers, variable speed drives and solar inverters from ABB, Eastron, Fronius, Schneider Electric and Siemens: 60+ maps today, listed on the register maps page. Other Modbus devices work with read_address and decode_registers, and maps are added through the open collection on GitHub.
- Does it work without the cloud?
- Yes. The server runs on your machine and talks to the devices directly. Your AI client decides where the conversation is processed; the device data goes only to the client that started the server.
- Is it free?
- Yes. It is open source under the Apache-2.0 licence, including for commercial use. The protocol drivers it uses are published as open-source NuGet packages too.