Proxus Industrial MCP Server

Name: Proxus Industrial MCP Server
Author: proxusiiotplatform

by proxusiiotplatformversion 0.1.0-beta.7i★ –iRuns on your computer

Registry nameio.github.proxusiiotplatform/proxus-mcp

Install

Overview

Description from the maker (original English)

Read-only Modbus TCP and OPC UA access to PLCs and industrial devices, with connection diagnostics

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "proxus": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"
      ]
    }
  }
}

Run this in your terminal

claude mcp add proxus -- docker run -i --rm ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "proxus": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "proxus": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/proxusiiotplatform/proxus-mcp:0.1.0-beta.7"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account proxusiiotplatform, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32489 servers in this category
Published to the registry more recently than 84% of the other 32489 servers in this category
Basic checks equal to or better than 100% of the other 32489 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Proxus Industrial MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0-beta.7) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Whisper

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Whisper

by whisper-sec

One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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
`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 to trusted/.
If the server answers BadCertificateUntrusted or BadSecurityChecksFailed, it has not trusted this client yet. proxus-mcp certificate --config 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 :/config ghcr.io/proxus-io/proxus-mcp: 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 (see tests/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 Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Whisper

README from the maker

Proxus Industrial MCP Server

Tools

Register maps

Verify a map on your device

OPC UA security

Install

Docker

Build

Claude Desktop

Tests

Licence