プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

OPC UA MCP Server

作者:IndustriAgentsバージョン 0.6.0i★ –iパソコンで動く
レジストリ名io.github.midhunxavier/opcua

インストール

概要

作者による説明(英語の原文)

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

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: パソコンで動く
  • トランスポート: stdio
  • カテゴリ: その他
  • 入力が必要なもの:OPCUA_SERVER_URL, OPCUA_CLIENT_KEY, OPCUA_PASSWORD, OPCUA_USER_KEY, OPCUA_PROFILE, OPCUA_AUDIT_CHAIN_KEY_FILE

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

  • 基本チェック:1項目中0項目に合格
  • あなたのパソコンで、あなたのユーザーと同じ権限(ファイル、ネットワーク、アプリ)で動きます。
  • 自分で入力するもの: 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

「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。

必要なもの

  • npmNode.jsのインストール(npxコマンドに必要)

どのアプリを使っていますか?

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

Claude Desktop → Settings → Developer → Edit Config を開き、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"
      }
    }
  }
}

ターミナルでこれを実行します

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

動かす前に、空欄の値を入力してください。

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.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"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "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"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

  • OPCUA_SERVER_URL 必須 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 秘密 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 秘密 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 秘密 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 必須 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 秘密 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.

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック

  • ! 注意

    作者とリポジトリが一致

    公開者(midhunxavier)がリポジトリの所有者(IndustriAgents)ではありません。別の人が登録した可能性があります

  • … 未チェック

    今もメンテナンスされている

    このリポジトリはまだGitHubから読み取っていません

  • … 未チェック

    ライセンスがある

    このリポジトリはまだGitHubから読み取っていません

  • – 対象外

    エンドポイントが応答する

    これはパソコンで動くため、インターネット上のエンドポイントはありません

  • – 対象外

    OAuthでサインイン

    パソコンで動き、代わりにローカルの設定を使います

  • … 未チェック

    ツールの説明に隠れた指示がない

    パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです

その他のほかのサーバーとの比較i

  • このカテゴリのほかの32709件のうち0%よりスターが多い
  • このカテゴリのほかの32709件のうち94%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの32709件のうち28%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

OPC UA MCP Serverは安全ですか?

当てはまる基本チェック1項目のうち0項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

入力が必要なもの:OPCUA_SERVER_URL, OPCUA_CLIENT_KEY, OPCUA_PASSWORD, OPCUA_USER_KEY, OPCUA_PROFILE, OPCUA_AUDIT_CHAIN_KEY_FILE

パソコンで動きますか、それともクラウドですか?

あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は–、最新バージョン(0.6.0)がレジストリに届いたのは一昨日です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。

代わりに使えるものは?

同じカテゴリには:Spec Driven Development, Remote Desktop Commander, SwarmMemo

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Remote Desktop Commander

作者:desktop-commander

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

クラウドで動く★ 211一昨日更新
インストール

SwarmMemo

作者:Hugo0

Talk with agent swarms: rooms, private messages and paid tasks for AI agents

クラウドで動く今日更新
インストール

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

🏭 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:

`

冒頭だけを表示しています。続きはリポジトリで読めます

PopNxに聞く