Proxus Industrial MCP Server
Read-only Modbus TCP and OPC UA access to PLCs and industrial devices, with connection diagnostics
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7claude mcp add proxus-industrial-mcp-server -- docker run -i --rm ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7{
"mcpServers": {
"proxus-industrial-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"
]
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Proxus 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 |
Nothing can write to a device.
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/proxusiiotplatform/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/proxusiiotplatform/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-arm64The 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.
Frequently asked questions
What is Proxus Industrial MCP Server?
Read-only Modbus TCP and OPC UA access to PLCs and industrial devices, with connection diagnostics
How do I install Proxus Industrial MCP Server?
It runs on your machine. In Claude Code: claude mcp add proxus-industrial-mcp-server -- docker run -i --rm ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Proxus Industrial MCP Server need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Proxus Industrial MCP Server open source?
Yes. Its code is on GitHub under the Apache-2.0 license.
Who maintains Proxus Industrial MCP Server?
It is published by proxusiiotplatform. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.