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
O
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.
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.
Tools
The tool list has not been reviewed yet.
Setup
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.
Fit and risk
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
Troubleshooting
- Confirm that the target OPC UA server is reachable
- Verify that the selected profile includes the tools needed for the workflow
- Check that the target server grants the permissions required for reads, writes, method calls, or subscriptions
- Check the .NET SDK, platform, and container environment; the README states that building requires the .NET 10 SDK
- If installation or client connection fails, verify the chosen installation method and client configuration; the supplied source includes no commands or configuration example
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
Supported clients
Supported clients have not been confirmed yet.