How do I install OPCUA?

OPCUA is a local plugin. Install it using npm package: opcua-mcp-server and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

What credentials does OPCUA need?

OPCUA requires the following credentials or environment variables: 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. You can find setup instructions on the server detail page.

What AI apps work with OPCUA?

OPCUA uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

OPCUA MCP Server

by IndustriAgents

Developer ToolsScan in ProgressMCP RegistryLocal

Free

Server data from the Official MCP Registry

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

About

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

Security Report

0.0

Use Caution0.0Moderate Risk

7 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Remote servers are capped at 8.0 because source code is not available for review. The score reflects endpoint verification only.

What You'll Need

Set these up before or after installing:

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 configured CA trust store.Optional

Environment variable: OPCUA_SERVER_URL

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 Python server only.Optional

Environment variable: OPCUA_PYTHON_BACKEND

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 than downgrading. None is unencrypted and unauthenticated, and keeps control tools blocked unless insecure control is explicitly allowed. An unknown policy stops the server at startup.Optional

Environment variable: OPCUA_SECURITY_POLICY

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 never downgrades a policy to signing only. Leave blank for SignAndEncrypt once a security policy is set, otherwise None.Optional

Environment variable: OPCUA_SECURITY_MODE

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.Optional

Environment variable: OPCUA_CLIENT_CERT

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 path that does not exist stops the server at startup.Required

Environment variable: OPCUA_CLIENT_KEY

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 for the subjectAltName URI of the client certificate.Optional

Environment variable: OPCUA_APPLICATION_URI

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 it, or OPCUA_SERVER_TRUST_STORE instead. Requires a security policy other than None. Unset, encryption protects against eavesdropping but not against an impostor endpoint, so control tools are refused unless OPCUA_SERVER_TRUST_STORE validates the server or OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL is set. Set without a security policy, it stops the server at startup rather than pinning nothing; a pinned certificate that has expired or is not yet valid refuses to connect.Optional

Environment variable: OPCUA_SERVER_CERT

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 expected server URI. Requires secured channel and OPCUA_SERVER_APPLICATION_URI; Python requires the maintained asyncua backend. Missing, stale, forged or revoked trust material refuses connection. Cannot be combined with an exact server certificate pin.Optional

Environment variable: OPCUA_SERVER_TRUST_STORE

ApplicationUri of the intended OPC UA server. Must match the peer certificate URI SAN and advertised application identity. Required with OPCUA_SERVER_TRUST_STORE.Optional

Environment variable: OPCUA_SERVER_APPLICATION_URI

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.Optional

Environment variable: OPCUA_USERNAME

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.Required

Environment variable: OPCUA_PASSWORD

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 other than None; cannot be combined with a username. Any of those combinations broken stops the server at startup.Optional

Environment variable: OPCUA_USER_CERT

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 the server.Required

Environment variable: OPCUA_USER_KEY

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 a tightly scoped OPC UA account. Unset fails closed to observe; an unknown profile stops the server at startup.Optional

Environment variable: OPCUA_PROFILE

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 what the file says. An unreadable or invalid file stops the server at startup.Optional

Environment variable: OPCUA_POLICY_FILE

Comma-separated tool allowlist. It can only narrow the selected profile, never widen it. An unknown tool name stops the server at startup.Optional

Environment variable: OPCUA_ALLOWED_TOOLS

Comma-separated exact node IDs the operator profile may write, as ns=2;i=5 or, stable across a server restart, nsu=<namespace-uri>;i=5 or a browse path from the Root folder such as /Objects/Line1/Setpoint. Setting it replaces the policy file's list, bounds included. Empty fails closed: operator can write nothing. A batch write with any target outside the list is refused before it reaches OPC UA.Optional

Environment variable: OPCUA_ALLOWED_WRITE_NODES

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 without | stops the server at startup.Optional

Environment variable: OPCUA_ALLOWED_METHODS

Let the operator profile act on alarms: acknowledge_alarm and every act_on_alarm action.Optional

Environment variable: OPCUA_ALLOW_ACKNOWLEDGE_ALARMS

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: writes, method calls and alarm actions then travel unauthenticated and unencrypted. Reported as control=INSECURE-OVERRIDE in the startup line, get_server_status and every audit record. Never enable it against production equipment.Optional

Environment variable: OPCUA_ALLOW_INSECURE_CONTROL

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 security policy; that is OPCUA_ALLOW_INSECURE_CONTROL. Fail-open override: writes, method calls and alarm actions are then encrypted to whichever server answered the endpoint, which may be an impostor. Reported as control=UNVERIFIED-OVERRIDE in the startup line, get_server_status and every audit record. Never enable it against production equipment.Optional

Environment variable: OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL

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 policy file has.Optional

Environment variable: OPCUA_ALLOW_OUT_OF_RANGE_WRITES

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 cannot be opened, or that is a symlink, not a regular file, another account's, or group/world-writable, stops the server rather than falling back to stderr alone. While set, a control call whose record cannot be written is refused (fail closed); reads continue.Optional

Environment variable: OPCUA_AUDIT_FILE

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 crash of this process. none can lose the records of control calls that already reached the plant if the machine loses power.Optional

Environment variable: OPCUA_AUDIT_FSYNC

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 without the key. Requires the audit file. Set without an audit file, or hmac-sha256 without a key file, stops the server. No chain detects a truncated tail.Optional

Environment variable: OPCUA_AUDIT_CHAIN

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 readable or writable by group or others stops the server. Refused unless the chain is hmac-sha256.Required

Environment variable: OPCUA_AUDIT_CHAIN_KEY_FILE

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.Optional

Environment variable: OPCUA_OPERATOR_ID

Wait before the first attempt to repair a dropped or refused connection, in milliseconds. It doubles with each further attempt.Optional

Environment variable: OPCUA_RECONNECT_INITIAL_DELAY_MS

Ceiling for the doubling retry delay, in milliseconds.Optional

Environment variable: OPCUA_RECONNECT_MAX_DELAY_MS

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 single call waits forever.Optional

Environment variable: OPCUA_RECONNECT_MAX_RETRY

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.Optional

Environment variable: OPCUA_SESSION_TIMEOUT_MS

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-midhunxavier-opcua": {
      "env": {
        "OPCUA_PROFILE": "your-opcua-profile-here",
        "OPCUA_PASSWORD": "your-opcua-password-here",
        "OPCUA_USERNAME": "your-opcua-username-here",
        "OPCUA_USER_KEY": "your-opcua-user-key-here",
        "OPCUA_USER_CERT": "your-opcua-user-cert-here",
        "OPCUA_AUDIT_FILE": "your-opcua-audit-file-here",
        "OPCUA_CLIENT_KEY": "your-opcua-client-key-here",
        "OPCUA_SERVER_URL": "your-opcua-server-url-here",
        "OPCUA_AUDIT_CHAIN": "your-opcua-audit-chain-here",
        "OPCUA_AUDIT_FSYNC": "your-opcua-audit-fsync-here",
        "OPCUA_CLIENT_CERT": "your-opcua-client-cert-here",
        "OPCUA_OPERATOR_ID": "your-opcua-operator-id-here",
        "OPCUA_POLICY_FILE": "your-opcua-policy-file-here",
        "OPCUA_SERVER_CERT": "your-opcua-server-cert-here",
        "OPCUA_ALLOWED_TOOLS": "your-opcua-allowed-tools-here",
        "OPCUA_SECURITY_MODE": "your-opcua-security-mode-here",
        "OPCUA_PYTHON_BACKEND": "your-opcua-python-backend-here",
        "OPCUA_ALLOWED_METHODS": "your-opcua-allowed-methods-here",
        "OPCUA_APPLICATION_URI": "your-opcua-application-uri-here",
        "OPCUA_SECURITY_POLICY": "your-opcua-security-policy-here",
        "OPCUA_SERVER_TRUST_STORE": "your-opcua-server-trust-store-here",
        "OPCUA_SESSION_TIMEOUT_MS": "your-opcua-session-timeout-ms-here",
        "OPCUA_ALLOWED_WRITE_NODES": "your-opcua-allowed-write-nodes-here",
        "OPCUA_RECONNECT_MAX_RETRY": "your-opcua-reconnect-max-retry-here",
        "OPCUA_AUDIT_CHAIN_KEY_FILE": "your-opcua-audit-chain-key-file-here",
        "OPCUA_ALLOW_INSECURE_CONTROL": "your-opcua-allow-insecure-control-here",
        "OPCUA_RECONNECT_MAX_DELAY_MS": "your-opcua-reconnect-max-delay-ms-here",
        "OPCUA_SERVER_APPLICATION_URI": "your-opcua-server-application-uri-here",
        "OPCUA_ALLOW_ACKNOWLEDGE_ALARMS": "your-opcua-allow-acknowledge-alarms-here",
        "OPCUA_ALLOW_OUT_OF_RANGE_WRITES": "your-opcua-allow-out-of-range-writes-here",
        "OPCUA_RECONNECT_INITIAL_DELAY_MS": "your-opcua-reconnect-initial-delay-ms-here",
        "OPCUA_ALLOW_UNVERIFIED_SERVER_CONTROL": "your-opcua-allow-unverified-server-control-here"
      },
      "args": [
        "-y",
        "opcua-mcp-server"
      ],
      "command": "npx"
    }
  }
}

Reviews

No reviews yet

Be the first to review this server!

4.8

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.