← Back to directory
O

OPC UA MCP Server

Official
Operate OPC UA through MCP for AI assistants.
Category
Dev Tools #348 of 438
Stars
★ 2.4k Very popular
Runtime
.NET · Prebuilt binary · Docker
Credentials
No credential needed
License
Other / unspecified
Last commit
41FMRS · D

This server is maintained by the OPC Foundation and targets OPC UA integration and industrial automation. The source clearly documents tool support, but provides no specific tool identifiers, transport values, client compatibility details, or installation configuration example.

Strongest · Maintenance 13/20 Weakest · Security and permissions 6/20

Reliability
7/20
Security and permissions
6/20
Maintenance
13/20
Documentation
8/20
Setup experience
7/20
Why each score
Reliability 7/20
The manifest declares tool capability and states that the default full profile registers all tools, with plausible operations such as browsing, reading, writing, method calls, and subscriptions. However, the supplied material contains no MCP-specific tests, initialization or tool-list handshake evidence, error-handling details, or dependency controls. This is a static review, so the score is kept below 12 and reduced for unverifiable execution behavior.
Security and permissions 6/20
The server can perform OPC UA reads, writes, method calls, administration, PubSub, and diagnostics, creating potential external side effects. The supplied material does not explain authentication, credential storage, authorization boundaries, data isolation, confirmation for dangerous operations, or network scope. No explicit red-line risk is evidenced, so this is not scored in the 0-4 range, but the missing least-privilege and confirmation evidence warrants substantial deductions.
Maintenance 13/20
The project is maintained by the OPC Foundation. The README describes an active 2.0 mainline, ongoing security and critical-bug fixes, contribution procedures, a CLA, and a SECURITY.md reporting channel; build, test, and release badges provide some maintenance evidence. The material gives no concrete release cadence, commit activity, issue-response data, or dependency-update policy. In addition, the object reports NOASSERTION while the manifest and README claim MIT, so license metadata and governance evidence are inconsistent.
Documentation 8/20
The main README provides project scope, supported platforms, build commands, sample applications, and a link to MCP-specific documentation, giving useful high-level coverage. It does not provide the MCP tool catalog, parameter constraints, authentication configuration, connection limits, permission model, cost, failure behavior, or troubleshooting evidence. The full/profile behavior also lacks a verifiable example, so the score remains modest.
Setup experience 7/20
The README identifies the .NET 10 SDK requirement and gives repository restore/build commands, and it states that the MCP server is available as a .NET tool or container. The supplied material lacks an actual installation command, mainstream MCP client configuration, server connection parameters, authentication setup, or an end-to-end validation procedure, leaving setup incomplete and potentially manual.

Static review · not runListed 2026-08-14

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • OPC UA integration in industrial control, manufacturing, energy, and IoT systems
  • Developers who need AI assistants to access OPC UA client operations
  • Teams building OPC UA tools or applications on .NET

Not for

  • Applications that do not use OPC UA
  • Deployments requiring documented tool identifiers or client configuration not present in the source
  • Environments requiring transport, authentication, or authorization details that the source does not specify

Required permissions

  • Requires access to the target OPC UA server
  • Read/write, method-call, and subscription operations require the corresponding permissions granted by the target OPC UA server; the precise permission model is not specified

Risks and side effects

  • Writing values or calling methods may change industrial-system or device state
  • Subscriptions and diagnostics may maintain connections or consume additional resources
  • The source does not specify authentication, authorization, or transport configuration; verify the target environment's security requirements before deployment
  • Repository metadata is NOASSERTION, while the project README and server manifest state MIT; confirm the applicable license before adoption

Setup

Before you start

Runtime:.NET · Prebuilt binary · Docker

The README states that the server is available as an installable .NET tool or container, and that its libraries can be embedded beside an application's own MCP tools. The supplied source does not provide installation commands or a client configuration example.

Check that it works

The opcua-mcp server's OPC UA tools should appear in your MCP client's tool list (the default 'full' profile registers every tool); browsing an OPC UA server's address space confirms the connection.

Troubleshooting

  1. Confirm that the target OPC UA server is reachable
  2. Verify that the selected profile includes the tools needed for the workflow
  3. Check that the target server grants the permissions required for reads, writes, method calls, or subscriptions
  4. Check the .NET SDK, platform, and container environment; the README states that building requires the .NET 10 SDK
  5. If installation or client connection fails, verify the chosen installation method and client configuration; the supplied source includes no commands or configuration example

Things to try

Once connected, you can ask your AI assistant things like:

  • Connect to my OPC UA server and browse its address space.
  • Read the current value of node ns=2;s=Channel1.Device1.Tag1.
  • Write the value 42 to that tag.
  • Call a method on the OPC UA server and create a subscription for data changes.

Use cases

Connect to OPC UA servers and browse address spaces
Read and write OPC UA values
Call OPC UA methods
Manage subscriptions
Expose OPC UA client operations to LLMs or Copilot through MCP

Overview

An MCP server included in the OPC Foundation's official OPC UA .NET Standard stack. It exposes OPC UA Part 4 service calls to AI assistants, including connecting to OPC UA servers, browsing address spaces, reading and writing values, calling methods, and managing subscriptions. Its tool catalog is profile-based across core, services, administration, pubsub, diagnostics, and full; the default full profile registers every tool.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

Source revision b25429bccc9f Data synced 2026-10-11 Read the FMRS scoring method