OPC Foundation OPC UA MCP

Who it's for

An engineer attaching an MCP client to OPC UA. Treat the write policy as the safety boundary: a gated write is still a write once you arm it.

Caveat / limitations

Package OPCFoundation.NetStandard.Opc.Ua.Mcp, run with dotnet tool exec or a global install as opcua-mcp. Profiles select a bounded tool catalog (core, machinery, alarms, history, and others). The default profile is broad, and UA services include writes, so treat the default as able to write. The repository is under the OPC Foundation MIT license. A WoT profile can also reach HTTP, MQTT, and Modbus TCP; that is optional and not the reason to install it.

Protocols

• OPC UAThe cross-vendor information model most modern PLCs, SCADA hosts, and historians can expose. Security policy, certificates, and user identity matter as much as the node id.

Sources

• McpREADMEhttps://github.com/OPCFoundation/UA-.NETStandard/blob/master/tools/Opc.Ua.Mcp/McpREADME.md
• UA-.NETStandardhttps://github.com/OPCFoundation/UA-.NETStandard

This page: https://otaihub.com/tools/opc-foundation-ua-mcp