Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

OPC UA MCP Server

by IndustriAgentsversion 0.6.0i★ –iRuns on your computer
Registry nameio.github.midhunxavier/opcua

Install

Overview

Description from the maker (original English)

Connect AI assistants to industrial OPC UA: browse, read, history, subscriptions, events and alarms.

PopNx MCP’s three pillars

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

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
  • You need to fill in: OPCUA_SERVER_URL, OPCUA_CLIENT_KEY, OPCUA_PASSWORD, OPCUA_USER_KEY, OPCUA_PROFILE, OPCUA_AUDIT_CHAIN_KEY_FILE

Install

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

Before you install

  • Basic checks: 0 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: OPCUA_SERVER_URL, OPCUA_PYTHON_BACKEND, OPCUA_SECURITY_POLICY, OPCUA_SECURITY_MODE, OPCUA_CLIENT_CERT, OPCUA_CLIENT_KEY, OPCUA_APPLICATION_URI, OPCUA_SERVER_CERT, OPCUA_SERVER_TRUST_STORE, OPCUA_SERVER_APPLICATION_URI, OPCUA_USERNAME, OPCUA_PASSWORD, OPCUA_USER_CERT, OPCUA_USER_KEY, OPCUA_PROFILE, OPCUA_POLICY_FILE, OPCUA_ALLOWED_TOOLS, OPCUA_ALLOWED_WRITE_NODES, OPCUA_ALLOWED_METHODS, OPCUA_ALLOW_ACKNOWLEDGE_ALARMS, OPCUA_ALLOW_INSECURE_CONTROL, OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL, OPCUA_ALLOW_OUT_OF_RANGE_WRITES, OPCUA_AUDIT_FILE, OPCUA_AUDIT_FSYNC, OPCUA_AUDIT_CHAIN, OPCUA_AUDIT_CHAIN_KEY_FILE, OPCUA_OPERATOR_ID, OPCUA_RECONNECT_INITIAL_DELAY_MS, OPCUA_RECONNECT_MAX_DELAY_MS, OPCUA_RECONNECT_MAX_RETRY, OPCUA_SESSION_TIMEOUT_MS

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

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": {
    "opcua": {
      "command": "npx",
      "args": [
        "-y",
        "opcua-mcp-server"
      ],
      "env": {
        "OPCUA_SERVER_URL": "your-value",
        "OPCUA_PYTHON_BACKEND": "your-value",
        "OPCUA_SECURITY_POLICY": "your-value",
        "OPCUA_SECURITY_MODE": "your-value",
        "OPCUA_CLIENT_CERT": "your-value",
        "OPCUA_CLIENT_KEY": "your-value",
        "OPCUA_APPLICATION_URI": "your-value",
        "OPCUA_SERVER_CERT": "your-value",
        "OPCUA_SERVER_TRUST_STORE": "your-value",
        "OPCUA_SERVER_APPLICATION_URI": "your-value",
        "OPCUA_USERNAME": "your-value",
        "OPCUA_PASSWORD": "your-value",
        "OPCUA_USER_CERT": "your-value",
        "OPCUA_USER_KEY": "your-value",
        "OPCUA_PROFILE": "your-value",
        "OPCUA_POLICY_FILE": "your-value",
        "OPCUA_ALLOWED_TOOLS": "your-value",
        "OPCUA_ALLOWED_WRITE_NODES": "your-value",
        "OPCUA_ALLOWED_METHODS": "your-value",
        "OPCUA_ALLOW_ACKNOWLEDGE_ALARMS": "your-value",
        "OPCUA_ALLOW_INSECURE_CONTROL": "your-value",
        "OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL": "your-value",
        "OPCUA_ALLOW_OUT_OF_RANGE_WRITES": "your-value",
        "OPCUA_AUDIT_FILE": "your-value",
        "OPCUA_AUDIT_FSYNC": "your-value",
        "OPCUA_AUDIT_CHAIN": "your-value",
        "OPCUA_AUDIT_CHAIN_KEY_FILE": "your-value",
        "OPCUA_OPERATOR_ID": "your-value",
        "OPCUA_RECONNECT_INITIAL_DELAY_MS": "your-value",
        "OPCUA_RECONNECT_MAX_DELAY_MS": "your-value",
        "OPCUA_RECONNECT_MAX_RETRY": "your-value",
        "OPCUA_SESSION_TIMEOUT_MS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add opcua --env OPCUA_SERVER_URL=your-value --env OPCUA_PYTHON_BACKEND=your-value --env OPCUA_SECURITY_POLICY=your-value --env OPCUA_SECURITY_MODE=your-value --env OPCUA_CLIENT_CERT=your-value --env OPCUA_CLIENT_KEY=your-value --env OPCUA_APPLICATION_URI=your-value --env OPCUA_SERVER_CERT=your-value --env OPCUA_SERVER_TRUST_STORE=your-value --env OPCUA_SERVER_APPLICATION_URI=your-value --env OPCUA_USERNAME=your-value --env OPCUA_PASSWORD=your-value --env OPCUA_USER_CERT=your-value --env OPCUA_USER_KEY=your-value --env OPCUA_PROFILE=your-value --env OPCUA_POLICY_FILE=your-value --env OPCUA_ALLOWED_TOOLS=your-value --env OPCUA_ALLOWED_WRITE_NODES=your-value --env OPCUA_ALLOWED_METHODS=your-value --env OPCUA_ALLOW_ACKNOWLEDGE_ALARMS=your-value --env OPCUA_ALLOW_INSECURE_CONTROL=your-value --env OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL=your-value --env OPCUA_ALLOW_OUT_OF_RANGE_WRITES=your-value --env OPCUA_AUDIT_FILE=your-value --env OPCUA_AUDIT_FSYNC=your-value --env OPCUA_AUDIT_CHAIN=your-value --env OPCUA_AUDIT_CHAIN_KEY_FILE=your-value --env OPCUA_OPERATOR_ID=your-value --env OPCUA_RECONNECT_INITIAL_DELAY_MS=your-value --env OPCUA_RECONNECT_MAX_DELAY_MS=your-value --env OPCUA_RECONNECT_MAX_RETRY=your-value --env OPCUA_SESSION_TIMEOUT_MS=your-value -- npx -y opcua-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "opcua": {
      "command": "npx",
      "args": [
        "-y",
        "opcua-mcp-server"
      ],
      "env": {
        "OPCUA_SERVER_URL": "your-value",
        "OPCUA_PYTHON_BACKEND": "your-value",
        "OPCUA_SECURITY_POLICY": "your-value",
        "OPCUA_SECURITY_MODE": "your-value",
        "OPCUA_CLIENT_CERT": "your-value",
        "OPCUA_CLIENT_KEY": "your-value",
        "OPCUA_APPLICATION_URI": "your-value",
        "OPCUA_SERVER_CERT": "your-value",
        "OPCUA_SERVER_TRUST_STORE": "your-value",
        "OPCUA_SERVER_APPLICATION_URI": "your-value",
        "OPCUA_USERNAME": "your-value",
        "OPCUA_PASSWORD": "your-value",
        "OPCUA_USER_CERT": "your-value",
        "OPCUA_USER_KEY": "your-value",
        "OPCUA_PROFILE": "your-value",
        "OPCUA_POLICY_FILE": "your-value",
        "OPCUA_ALLOWED_TOOLS": "your-value",
        "OPCUA_ALLOWED_WRITE_NODES": "your-value",
        "OPCUA_ALLOWED_METHODS": "your-value",
        "OPCUA_ALLOW_ACKNOWLEDGE_ALARMS": "your-value",
        "OPCUA_ALLOW_INSECURE_CONTROL": "your-value",
        "OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL": "your-value",
        "OPCUA_ALLOW_OUT_OF_RANGE_WRITES": "your-value",
        "OPCUA_AUDIT_FILE": "your-value",
        "OPCUA_AUDIT_FSYNC": "your-value",
        "OPCUA_AUDIT_CHAIN": "your-value",
        "OPCUA_AUDIT_CHAIN_KEY_FILE": "your-value",
        "OPCUA_OPERATOR_ID": "your-value",
        "OPCUA_RECONNECT_INITIAL_DELAY_MS": "your-value",
        "OPCUA_RECONNECT_MAX_DELAY_MS": "your-value",
        "OPCUA_RECONNECT_MAX_RETRY": "your-value",
        "OPCUA_SESSION_TIMEOUT_MS": "your-value"
      }
    }
  }
}

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": {
    "opcua": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "opcua-mcp-server"
      ],
      "env": {
        "OPCUA_SERVER_URL": "your-value",
        "OPCUA_PYTHON_BACKEND": "your-value",
        "OPCUA_SECURITY_POLICY": "your-value",
        "OPCUA_SECURITY_MODE": "your-value",
        "OPCUA_CLIENT_CERT": "your-value",
        "OPCUA_CLIENT_KEY": "your-value",
        "OPCUA_APPLICATION_URI": "your-value",
        "OPCUA_SERVER_CERT": "your-value",
        "OPCUA_SERVER_TRUST_STORE": "your-value",
        "OPCUA_SERVER_APPLICATION_URI": "your-value",
        "OPCUA_USERNAME": "your-value",
        "OPCUA_PASSWORD": "your-value",
        "OPCUA_USER_CERT": "your-value",
        "OPCUA_USER_KEY": "your-value",
        "OPCUA_PROFILE": "your-value",
        "OPCUA_POLICY_FILE": "your-value",
        "OPCUA_ALLOWED_TOOLS": "your-value",
        "OPCUA_ALLOWED_WRITE_NODES": "your-value",
        "OPCUA_ALLOWED_METHODS": "your-value",
        "OPCUA_ALLOW_ACKNOWLEDGE_ALARMS": "your-value",
        "OPCUA_ALLOW_INSECURE_CONTROL": "your-value",
        "OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL": "your-value",
        "OPCUA_ALLOW_OUT_OF_RANGE_WRITES": "your-value",
        "OPCUA_AUDIT_FILE": "your-value",
        "OPCUA_AUDIT_FSYNC": "your-value",
        "OPCUA_AUDIT_CHAIN": "your-value",
        "OPCUA_AUDIT_CHAIN_KEY_FILE": "your-value",
        "OPCUA_OPERATOR_ID": "your-value",
        "OPCUA_RECONNECT_INITIAL_DELAY_MS": "your-value",
        "OPCUA_RECONNECT_MAX_DELAY_MS": "your-value",
        "OPCUA_RECONNECT_MAX_RETRY": "your-value",
        "OPCUA_SESSION_TIMEOUT_MS": "your-value"
      }
    }
  }
}

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.

Values you fill in

  • OPCUA_SERVER_URL required env
    URL of the OPC UA server to connect to, including any path the server expects. Read once at startup: one process serves one endpoint. Verify who answers with an exact server certificate pin or a conf…
  • OPCUA_PYTHON_BACKEND env
    Select the Python client implementation. The maintained asyncua client is the default; legacy provides the one-release rollback path for uncovered vendor incompatibilities. This setting affects the P…
  • OPCUA_SECURITY_POLICY env
    Encryption suite to negotiate for the secure channel. Anything other than None needs a client certificate and key. The two AES suites are Node-only: the Python runtime refuses them at startup rather…
  • OPCUA_SECURITY_MODE env
    Message security mode for the secure channel. Sign authenticates messages without encrypting them. A policy with mode None, or a mode without a policy, stops the server at startup; leaving it blank n…
  • OPCUA_CLIENT_CERT env
    Path to the certificate (PEM or DER) this client presents as its application identity. Required by any security policy other than None. A path that does not exist stops the server at startup.
  • OPCUA_CLIENT_KEY secret env
    Path to the private key matching the client certificate. A path, never key material. Whoever can read the file can impersonate this client: keep it readable only by the account running the server. A…
  • OPCUA_APPLICATION_URI env
    Application URI announced to the server. Set it only for a certificate that carries no URI of its own. A configured URI that conflicts with the certificate is refused before connecting. Leave blank f…
  • OPCUA_SERVER_CERT env
    Path to the OPC UA server's own certificate (PEM or DER), pinned: a server presenting any other certificate cannot complete the handshake. Control tools (writes, method calls, alarm actions) require…
  • OPCUA_SERVER_TRUST_STORE env
    Directory with trusted/certs root CAs, issuers/certs intermediate CAs, and trusted/crl plus issuers/crl signed current revocation lists. Authenticate the OPC UA peer by its validated chain and expect…
  • OPCUA_SERVER_APPLICATION_URI env
    ApplicationUri of the intended OPC UA server. Must match the peer certificate URI SAN and advertised application identity. Required with OPCUA_SERVER_TRUST_STORE.
  • OPCUA_USERNAME env
    OPC UA username. The session is anonymous when unset. Cannot be combined with a user certificate. Requires a password; either one alone stops the server at startup.
  • OPCUA_PASSWORD secret env
    Password for the username. Without a security policy it crosses the network in clear text. Supply it through the client's secret storage, never on a command line.
  • OPCUA_USER_CERT env
    Path to the certificate identifying the user, for X.509 user authentication: a different key pair from the client certificate, which secures the channel. Requires the user key and a security policy o…
  • OPCUA_USER_KEY secret env
    Path to the private key for the user certificate. It signs the server's challenge and is never sent. Whoever can read the file can log in as this user: keep it readable only by the account running th…
  • OPCUA_PROFILE required env
    Which tools are offered. observe reads, browses, reads history and monitors; operator adds explicitly allowlisted writes, method calls and alarm actions; full exposes every tool and is meant only for…
  • OPCUA_POLICY_FILE env
    Path to a version-1 JSON policy file, the only place per-node value bounds, writable_subtrees, preconditions, the alarm scope and deny_read can be set. Every policy variable that is set overrides wha…
  • OPCUA_ALLOWED_TOOLS env
    Comma-separated tool allowlist. It can only narrow the selected profile, never widen it. An unknown tool name stops the server at startup.
  • OPCUA_ALLOWED_WRITE_NODES env
    Comma-separated exact node IDs the operator profile may write, as ns=2;i=5 or, stable across a server restart, nsu= ;i=5 or a browse path from the Root folder such as /Objects/Line1/Setpoint. Setting…
  • OPCUA_ALLOWED_METHODS env
    Comma-separated object_node_id|method_node_id pairs the operator profile may call. Either half may be a browse path from the Root folder. Empty fails closed: operator can call nothing. An entry witho…
  • OPCUA_ALLOW_ACKNOWLEDGE_ALARMS env
    Let the operator profile act on alarms: acknowledge_alarm and every act_on_alarm action.
  • OPCUA_ALLOW_INSECURE_CONTROL env
    Permit control tools on an OPC UA channel with no security policy (None). Does not cover a secured channel to an unverified server; that is OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL. Fail-open override:…
  • OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL env
    Permit control tools on a secured OPC UA channel whose server is not authenticated: neither pinned with OPCUA_SERVER_CERT nor validated by OPCUA_SERVER_TRUST_STORE. Does not cover a channel with no s…
  • OPCUA_ALLOW_OUT_OF_RANGE_WRITES env
    Allow a write outside the EURange the OPC UA server itself published for the node. A published InstrumentRange still applies. Fail-open override: it discards the only value bound a deployment with no…
  • OPCUA_AUDIT_FILE env
    Path to an append-only file for the control audit trail, one JSON object per line, written beside stderr. Created owner-only (0600) if it does not exist; reopened when rotated away. A file that canno…
  • OPCUA_AUDIT_FSYNC env
    When an audit-file record counts as written. always fsyncs each record before the control call proceeds, so it survives a power loss; none leaves it to the operating system, so it survives only a cra…
  • OPCUA_AUDIT_CHAIN env
    Adds seq, prev_hash and hash to every audit record so edits, deletions and reordering can be detected with --verify-audit. sha256 catches accidental or naive edits; hmac-sha256 also resists anyone wi…
  • OPCUA_AUDIT_CHAIN_KEY_FILE secret env
    Path to the HMAC key for the hmac-sha256 audit chain: at least 32 bytes, for example from openssl rand -hex 32. Surrounding whitespace is ignored. Whoever can read the key can forge the chain: a key…
  • OPCUA_OPERATOR_ID env
    Label stamped on every audit record as operator_label, so a shipped log says which deployment a control call came from. Configured, never verified: it is not an identity, and mcp_principal stays null.
  • OPCUA_RECONNECT_INITIAL_DELAY_MS env
    Wait before the first attempt to repair a dropped or refused connection, in milliseconds. It doubles with each further attempt.
  • OPCUA_RECONNECT_MAX_DELAY_MS env
    Ceiling for the doubling retry delay, in milliseconds.
  • OPCUA_RECONNECT_MAX_RETRY env
    Retries after the first attempt, per connection round, before a tool call gives up: a whole number from -1 to 1000. 0 never retries; -1 never stops trying, in bounded rounds of four retries so no sin…
  • OPCUA_SESSION_TIMEOUT_MS env
    Session lifetime asked of the OPC UA server, in milliseconds. It also sets the keep-alive period, so it decides how quickly an idle connection notices the server has gone.

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 7, 2026

  • ! Caution

    Maker matches the repo

    The publisher (midhunxavier) is not the repo owner (IndustriAgents); someone else may have listed it

  • … 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 18348 servers in this category
  • Published to the registry more recently than 95% of the other 18348 servers in this category
  • Basic checks equal to or better than 24% of the other 18348 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 OPC UA MCP Server safe?

It passed 0 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?

You need to fill in: OPCUA_SERVER_URL, OPCUA_CLIENT_KEY, OPCUA_PASSWORD, OPCUA_USER_KEY, OPCUA_PROFILE, OPCUA_AUDIT_CHAIN_KEY_FILE

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.6.0) reached the registry 2 days ago.

Which apps can use it?

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

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, 好縮 Short

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 2 days ago
Install

好縮 Short

by gooonamee

Smart URL shortener: create, tag and track short links on s.gooo.name.

Runs in the 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.

🏭 OPC UA MCP Server

Let Claude, Codex, Gemini and any other MCP agent read sensors, browse the plant and — only when you allow it — control equipment on any OPC UA server.

[▶ Try it without hardware](#try-it-without-a-plant) — a simulated plant ships in this repository

Quick start · Connect your agent · Tools · Production · Docs · Contributing

Official MCP Registry · Glama · HardwareMCP

Every tool call and value above is a real response from the bundled simulator, recorded through the Python bridge under the read-only observe profile; the question and answer text are scripted. Rebuild it with scripts/readme_demo.py.

This project is a bridge between an AI agent and an OPC UA server. OPC UA is the protocol used to expose industrial equipment and its data; MCP (Model Context Protocol) lets an agent call tools to work with that data. The bridge runs on your computer and connects to an existing OPC UA server, or to a local simulator for a first test.

Your MCP client starts the bridge as a local stdio process: it exchanges MCP messages over standard input and output. One process connects one client context to one OPC UA endpoint. Use a separate process for each endpoint. Remote MCP and shared multi-client operation are gated by the identity and isolation RFC.

Features

  • 🔌 Any OPC UA server — PLC, SCADA gateway or historian. Nothing to install on the plant side.
  • 🧰 The whole operator toolkit — read, browse, history and aggregates, subscriptions, events and alarms, writes and method calls.
  • 🛡️ Read-only by default — writes and method calls need an explicit control profile and an authenticated server (pinned certificate or CA trust store). The operator profile also requires allowlisted targets, and every control call is audited.
  • 🐍 Python or Node — two first-class runtimes with the same tool contract. Use whichever you have, accounting for the documented runtime differences.
  • 📦 One-file Claude Desktop install — a .mcpb bundle with nothing else to set up.
flowchart LR

A["AI agent (Claude, Codex, Gemini, Cursor…)"] -->|MCP over stdio| B["OPC UA MCP Server (Python or Node)"] B -->|OPC UA| C["OPC UA server (PLC / SCADA / historian)"]

Quick start

Follow these steps in order: choose an installation, start or identify an OPC UA server, configure your MCP client, then check the connection. You need an MCP client such as one of the agents listed below.

1. Choose an installation

Choose one runtime; you do not need both. The package routes fetch the server on demand, so you do not need to clone this repository to use an existing OPC UA server.

RoutePrerequisitesCommand your MCP client launches
Node packageNode.js 22.13+, including npm and npxnpx -y opcua-mcp-server
Python packagePython 3.10+ and uv (which supplies uvx)uvx opcua-mcp-server
Claude Desktop bundleClaude Desktop; no separate Node or Python installationInstall the .mcpb file as described below
Single-file executableDownload for your platform; no Node or Python installationUse its absolute path as the client command; see installation instructions

For a package route, check that it can run from your terminal. Run the command for your chosen runtime:

# Node

npx -y opcua-mcp-server --version

Or Python

uvx opcua-mcp-server --version

These commands print a version and exit. In normal use, your MCP client launches the server without --version; you do not also start the bridge in a separate terminal. A bridge started by itself waits for MCP messages, rather than showing an interactive prompt or a web page.

2. Choose an OPC UA endpoint

For an existing server, get its endpoint URL, including any path, from its administrator (for example opc.tcp://192.168.0.10:4840). The bridge reads it from OPCUA_SERVER_URL, which you set in your MCP client's configuration in step 3. If unset, the default is opc.tcp://localhost:4840.

The default profile is observe (read-only), and the default OPC UA connection is unencrypted and anonymous. Use those defaults for the local mock. For real equipment, prepare the security configuration before connecting.

Try it without a plant

If you do not have an OPC UA server, start the bundled simulated plant. This optional route needs Git, Python 3.10+ and uv, even if you chose the Node bridge. Run these commands in a terminal:

git clone https://github.com/IndustriAgents/OPCUA-MCP.git

cd OPCUA-MCP uv sync --all-packages uv run --no-sync opcua-mock-server

Wait for Server is running and ready for connections, then leave this terminal running. The mock listens on port 4840; use opc.tcp://localhost:4840/freeopcua/server/ as your endpoint. Stop it with Ctrl-C when finished. If the port is busy, choose another port with uv run --no-sync opcua-mock-server --endpoint opc.tcp://127.0.0.1:14840/freeopcua/server/ and use that URL in your client configuration.

The plant supports browsing, sensor reads, data-change subscriptions, raw value history, plain events and event history. It also has writable actuators and methods, subject to the bridge's control policy. It does not implement processed aggregates or Alarms & Conditions: its plain alarm events cannot be listed as retained conditions, acknowledged or acted on with alarm-action tools. Use the separate mocks for those operations:

MockEndpointCoverage
Plantopc.tcp://localhost:4840/freeopcua/server/Sensors, actuators, methods, raw history, subscriptions and plain events
Aggregatesopc.tcp://localhost:4841/UA/AggregateProcessed history, such as average buckets
Alarmsopc.tcp://localhost:4842/UA/AlarmsActive conditions and acknowledgement

The separate mocks need Node and npm; their READMEs give installation and startup commands. The MCP Inspector walkthrough has more examples, and the compatibility matrix records tested coverage.

Connect your agent

3. Configure the client and launch the bridge

Pick one client below. The examples use the local plant endpoint from step 2; replace opc.tcp://localhost:4840/freeopcua/server/ with your endpoint if needed. For a secure connection, add the settings from Going to production to the same env block (or the bundle's settings fields).

To use Python in a JSON configuration, set "command": "uvx" and "args": ["opcua-mcp-server"]. In a CLI registration command, replace npx -y opcua-mcp-server with uvx opcua-mcp-server. In TOML, use command = "uvx" and args = ["opcua-mcp-server"].

Claude Desktop

Easiest — the bundle. Download opcua-mcp-server- .mcpb from the latest release, drag it into Settings → Extensions, and fill in OPC UA endpoint. No Node, no Python, no JSON.

Or let the server write the config (needs Node or Python):

npm install -g opcua-mcp-server      # or: uv tool install opcua-mcp-server

opcua-mcp-server --install claude-desktop --url opc.tcp://localhost:4840/freeopcua/server/ --dry-run

It checks the config with the server's own startup validation and writes absolute paths, because Claude Desktop does not inherit your shell's PATH. The profile defaults to read-only; encryption, a pinned server certificate, a control profile, a policy file and an audit file are all flags, and passwords are never taken as flags. Check the preview, then repeat the command without --dry-run to write the configuration and restart Claude Desktop. Every flag and safety rule, editing claude_desktop_config.json by hand, and fixing a server that fails to start: docs/install.md.

Claude Code

claude mcp add opcua -e OPCUA_SERVER_URL=opc.tcp://localhost:4840/freeopcua/server/ -- npx -y opcua-mcp-server

Add --scope project to share it with your team through .mcp.json.

OpenAI Codex

codex mcp add opcua --env OPCUA_SERVER_URL=opc.tcp://localhost:4840/freeopcua/server/ -- npx -y opcua-mcp-server

Or add it to ~/.codex/config.toml:

[mcp_servers.opcua]

command = "npx" args = ["-y", "opcua-mcp-server"] env = { OPCUA_SERVER_URL = "opc.tcp://localhost:4840/freeopcua/server/" }

Or let the server write that entry, with the same checks as for Claude Desktop: opcua-mcp-server --install codex --url opc.tcp://localhost:4840/freeopcua/server/ --dry-run. This installer command requires a permanent package installation first: npm install -g opcua-mcp-server or uv tool install opcua-mcp-server. Check the preview and repeat without --dry-run to write it.

Gemini CLI

Add to ~/.gemini/settings.json, or .gemini/settings.json in a project:

{

"mcpServers": { "opcua": { "command": "npx", "args": ["-y", "opcua-mcp-server"], "env": { "OPCUA_SERVER_URL": "opc.tcp://localhost:4840/freeopcua/server/" } } } }

Google Antigravity

In the agent panel, open ⋯ → MCP Servers → Manage MCP Servers → View raw config, add the entry below to mcp_config.json, and restart Antigravity:

{

"mcpServers": { "opcua": { "command": "npx", "args": ["-y", "opcua-mcp-server"], "env": { "OPCUA_SERVER_URL": "opc.tcp://localhost:4840/freeopcua/server/" } } } }

Cursor

Add to ~/.cursor/mcp.json, or .cursor/mcp.json in a project:

{

"mcpServers": { "opcua": { "command": "npx", "args": ["-y", "opcua-mcp-server"], "env": { "OPCUA_SERVER_URL": "opc.tcp://localhost:4840/freeopcua/server/" } } } }

VS Code (GitHub Copilot)

Add to .vscode/mcp.json — note the top-level key is servers:

`

Only the beginning is shown; read the rest in the repo

Ask PopNx