Proxus Industrial MCP server
Commit Nov 9, 2026Provides AI assistants with read-only access to industrial devices via Modbus TCP and OPC UA, including connection diagnostics and register mapping.
Also known as proxusiiotplatform/proxus-mcp, proxus-mcp
- Stars
- 0
- Tools
- 12
- Downloads, 30 days
- —
- Latest version
- 0.1.0-beta.7
- Last commit
- Nov 9, 2026
- License
- Apache-2.0
What is Proxus Industrial MCP?
Proxus Industrial provides AI assistants with read-only access to industrial devices via Modbus TCP and OPC UA, including connection diagnostics and register mapping. It exposes 12 tools, such as list_devices, read_address, watch_address.
Summary generated from the project's README
About Proxus Industrial MCP server
Proxus Industrial MCP Server provides AI assistants like Claude Desktop, Cursor, and VS Code with read-only access to industrial hardware. It connects to devices using Modbus TCP and OPC UA protocols, supporting various security policies and encryption methods. Users can configure specific devices via a JSON configuration file, providing host addresses and register maps to help the assistant interpret raw data.
This server is designed for engineers and developers who need to bridge the gap between LLMs and factory floor equipment. It includes specialized tools for monitoring data, such as watching Modbus addresses or OPC UA variables for specific durations to summarize movement. It also features a diagnostic tool to troubleshoot connection failures by checking TCP handshakes, security certificates, and login credentials step by step.
To maintain security, the server handles OPC UA certificates through a local directory structure and retrieves passwords from environment variables rather than configuration files. The system also includes a library of register maps for common hardware, allowing the assistant to read meaningful engineering values like voltage instead of raw hex codes.
Written from the project's README. Every use case is checked against a quote from it.
How to install Proxus Industrial MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Proxus Industrial MCP in Claude Code
$ claude mcp add proxus-mcp -- docker run -i --rm ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7Install Proxus Industrial MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"proxus-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"
]
}
}
}Install Proxus Industrial MCP in VS Code
.vscode/mcp.json
{
"servers": {
"proxus-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"
]
}
}
}Install Proxus Industrial MCP in VS Code CLI
$ code --add-mcp '{"name":"proxus-mcp","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"]}'Install Proxus Industrial MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"proxus-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"
]
}
}
}Install Proxus Industrial MCP in Codex
$ codex mcp add proxus-mcp -- docker run -i --rm ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7Install Proxus Industrial MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.proxus-mcp] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"]
Install Proxus Industrial MCP in Gemini CLI
$ gemini mcp add -s user proxus-mcp docker -- run -i --rm ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7Install Proxus Industrial MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"proxus-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"
]
}
}
}Proxus Industrial MCP tools 12
Detected from the READMElist_devicesread_addresswatch_addressdecode_registersbrowseread_nodeswatch_nodesdiagnose_connectionfind_device_mapget_device_mapread_namedverify_device_map
| list_devices | — | |
| read_address | — | |
| watch_address | — | |
| decode_registers | — | |
| browse | — | |
| read_nodes | — | |
| watch_nodes | — | |
| diagnose_connection | — | |
| find_device_map | — | |
| get_device_map | — | |
| read_named | — | |
| verify_device_map | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableproxusiiotplatform/proxus-mcp is public and reachablegithub.com/proxusiiotplatform/proxus-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-09github.com/proxusiiotplatform/proxus-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model12 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubProxus Industrial MCP Server
Gives AI assistants such as Claude Desktop, Cursor and VS Code read-only access to industrial devices. Supports Modbus TCP and OPC UA (Basic256Sha256, Aes128_Sha256_RsaOaep or Aes256_Sha256_RsaPss with Sign or SignAndEncrypt, or unsecured; anonymous or user-name login).
Condensed from a real session against simulated devices (docs/demo.json). More at proxus.io/tools/industrial-mcp-server.
Tools
| Tool | What it does |
|---|---|
list_devices |
Configured devices, endpoint, ISA-95 path, connection state |
read_address |
Raw registers or bits: hr:0, ir:10, coil:5, di:0 or 40001 |
watch_address |
Polls a Modbus address for 1–60 s and summarises how it moved, decoded as uint16, int16, uint32, int32 or float32 in any byte order |
decode_registers |
Up to 16 registers read every common way: int16/32, uint, float32 in ABCD/CDAB/BADC/DCBA, float64 in both word orders |
browse |
Children of an OPC UA node (default: Objects folder) |
read_nodes |
Up to 50 OPC UA variables with data type, quality, status code and source timestamp |
watch_nodes |
Watches up to 20 OPC UA variables for 1–60 s through a subscription: every change, plus first, last, min, max and average |
diagnose_connection |
Why a device can't be reached: name, TCP, protocol handshake, security and certificates, login, a test read, identity and clock, step by step with the next thing to try |
find_device_map |
Searches the register map library by vendor, model or alias, e.g. PM5560 |
get_device_map |
A map's registers (key, address, type, byte order, unit, scale), filtered by a search word |
read_named |
Reads registers by key from the device's map and returns engineering values with units |
verify_device_map |
Checks the device's map against the real device and prepares a hardware verification report (read-only) |
Nothing can write to a device.
Register maps
With a register map the assistant reads voltage_l1_n instead of guessing that hr:0-1 is a word-swapped float.
A map lists every register of a device model: address, data type, byte order, scale (fixed, or a SunSpec scale-factor
register), unit and the meaning of enumerated values, with the vendor document it comes from. The binaries include the
open Modbus Register Maps collection (energy meters, power
analysers, drives, inverters); each release also attaches it as register-maps.json.gz.
Give a Modbus device its map in the configuration, by id or as the path of a map's JSON file:
"meter-1": { "protocol": "modbus-tcp", "host": "192.168.10.40", "map": "schneider-electric/pm5500-pm5600-pm5700" }
maps_dir adds maps (or replaces built-in ones with the same id) from a folder of JSON files, as
python3 tools/maps.py build in the collection writes them. A map that does not exist stops the server at start-up with the reason. Maps tell the assistant how to
read a register, never to write one: read_named only reads.
Verify a map on your device
Most maps are transcribed from vendor documents. Ask your assistant to verify the device's map: verify_device_map
reads every register once (read-only), checks that the values are plausible (floats, frequency, voltage, power factor,
energy counters, model) and asks you to compare two values with the device's display. The result is a report and a
link that opens a prefilled issue in the map collection; you submit it under your own GitHub account, and a bot adds
you to the map's verified list. Nothing is sent without you, and the report holds check results only, no addresses,
host names or serial numbers.
OPC UA security
Set security_mode (sign_and_encrypt, sign or none) and security_policy (Basic256Sha256,
Aes128_Sha256_RsaOaep or Aes256_Sha256_RsaPss) per device. Certificates live in pki_dir (default pki/ next to the configuration file),
in the layout most OPC UA tools use:
| Folder | Holds |
|---|---|
own/ |
This server's application certificate, created on first use (private key readable only by you) |
trusted/ |
Server certificates you approved |
rejected/ |
Server certificates seen but not approved |
Trust is never automatic, in either direction:
- On the first connection the server's certificate lands in
rejected/and the tool answers with its SHA-256 thumbprint. Confirm the thumbprint with the server's administrator, then move the file totrusted/. - If the server answers
BadCertificateUntrustedorBadSecurityChecksFailed, it has not trusted this client yet.proxus-mcp certificate --config <file>prints this server's certificate file and thumbprint to trust on the server.
Passwords never go in the configuration file: password_env names the environment variable that holds them. Errors
carry the OPC UA StatusCode name, the specification's description and a suggested next step.
Install
Download the archive for your platform from the releases page, unpack it, and point your MCP client
at the proxus-mcp binary (see Claude Desktop below). Each archive has a .sha256 file next to it. The binaries are
not code-signed yet: on macOS run xattr -d com.apple.quarantine proxus-mcp once after unpacking, and on Windows
choose "More info, Run anyway" the first time.
proxus-mcp --version prints the version.
Docker
docker run -i --rm -v "$PWD:/config" ghcr.io/proxus-io/proxus-mcp:<version>
The image reads /config/proxus-mcp.json and speaks MCP over stdin/stdout, so an MCP client starts it with
docker as the command and run -i --rm -v <folder>:/config ghcr.io/proxus-io/proxus-mcp:<version> as the
arguments. Devices on the host are reachable as host.docker.internal; on Linux add --network host to reach the
plant network directly. Images are published for linux/amd64 and linux/arm64.
Build
Needs the .NET 10 SDK. The protocol drivers come from the Proxus.Drivers NuGet packages (Apache-2.0).
dotnet publish src/Proxus.Mcp.Server -c Release -r osx-arm64 -o artifacts/osx-arm64
The result is one native file, artifacts/osx-arm64/proxus-mcp (about 10 MB).
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"proxus": {
"command": "/absolute/path/to/proxus-mcp",
"args": ["--config", "/absolute/path/to/proxus-mcp.json"]
}
}
}
Copy proxus-mcp.example.json as a starting configuration.
Tests
dotnet test tests/Proxus.Mcp.Tests: unit tests, no devices needed.tests/smoke/run_all.sh: the published binary against Modbus and OPC UA simulators (seetests/smoke/README.md).- CI (
.github/workflows/ci.yml) runs both and publishes Native AOT binaries for linux-x64, linux-arm64, win-x64 and osx-arm64.
Licence
Apache-2.0, see LICENSE.
Proxus Industrial MCP questions
How do I add Proxus Industrial MCP to Claude Code?
Run claude mcp add proxus-mcp -- docker run -i --rm ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7 in your terminal. Add --scope user to make it available in every project.
How do I add Proxus Industrial MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Proxus Industrial MCP provide?
It exposes 12 tools, including list_devices, read_address, watch_address, decode_registers, browse.
Can the server write data to my industrial devices?
No, the server is strictly read-only and nothing can write to a device.
How does the server handle OPC UA security?
It supports various security modes and policies, including sign and encrypt, and uses a PKI directory for managing application and trusted certificates.
What happens if a device cannot be reached?
The server includes a diagnostic tool that provides a step-by-step analysis of why a connection failed, covering TCP, protocol handshakes, security, and login.
How are passwords managed in the configuration?
Passwords are not stored in the configuration file; instead, you specify an environment variable that holds them.