UA-.NETStandard/tools/Opc.Ua.Mcp/McpREADME.md

OPC UA MCP Server

A Model Context Protocol (MCP) server that exposes OPC UA Part 4 service calls as MCP tools, enabling AI assistants (Claude, GitHub Copilot, VS Code, etc.) to interact with OPC UA servers.

Run without installing (.NET 10 SDK)

dotnet tool exec OPCFoundation.NetStandard.Opc.Ua.Mcp

# Short form
dnx OPCFoundation.NetStandard.Opc.Ua.Mcp

Install globally

dotnet tool install --global OPCFoundation.NetStandard.Opc.Ua.Mcp

The tool includes Robotics, Vision and the AMB, Machinery, Scales, Pumps, Device Integration, ISA-95, Positioning, MachineTool (with bundled WMTP), GMS, CranesHoists, WoT and xRegistry profiles. Profiles compose, for example --profile machinery,isa95, --profile machinetool,gms,craneshoists, or --profile core,wot,xregistry,wot-documents. wot-documents needs no UA connection. Additional profiles expose GDS/credential issuance, roles/users, files, alarms, history, schemas, PubSub configuration/bridges/SKS and live WoT execution.

Usage

The examples below assume a global installation. For run-on-demand use, replace opcua-mcp with dnx OPCFoundation.NetStandard.Opc.Ua.Mcp --.

# stdio transport (default) — for Claude Desktop, VS Code, Copilot
opcua-mcp

# Streamable HTTP transport (exposed only at /mcp) — for remote clients
opcua-mcp --transport http --port 5100

# --transport sse is a deprecated alias for --transport http

Client configuration

For on-demand execution, clients supporting command/argument arrays can use:

{
  "mcpServers": {
    "opcua": {
      "command": "dotnet",
      "args": ["tool", "exec", "OPCFoundation.NetStandard.Opc.Ua.Mcp", "--", "--profile", "core"]
    }
  }
}

After global installation, Claude Desktop and Cursor can use:

{
  "mcpServers": {
    "opcua": { "command": "opcua-mcp" }
  }
}

Claude's file is typically %APPDATA%\Claude\claude_desktop_config.json on Windows or ~/Library/Application Support/Claude/claude_desktop_config.json on macOS. Use the corresponding MCP settings in Cursor.

VS Code / GitHub Copilot uses .vscode/mcp.json:

{
  "servers": {
    "opcua": { "command": "opcua-mcp" }
  }
}

Host authority and shared transfer configuration are documented in the Core package reference; document dependency configuration is in the WoT package reference.

Tools

The server exposes tools through a tool profile — a bounded, named catalog selected with --profile <name>. Run opcua-mcp --help for the current profile names. Profiles can be composed, for example --profile vision,robotics. full is the default; the other profiles expose smaller focused subsets. See the full documentation for the profile-to-tool mapping.

Host-disabled privileged/live tools stay hidden even under full. Explicit host capabilities and exact caller/session/network grants are required to enable them; a profile is never an execution grant.

Tools in the full profile cover all OPC UA Part 4 service sets:

• Connection: Connect, ConnectCertificate, Disconnect, GetConnectionStatus
• Attribute: Read, Write, HistoryRead, HistoryUpdate
• View: Browse, BrowseNext, TranslateBrowsePaths, RegisterNodes, UnregisterNodes, QueryFirst, QueryNext
• Node Management: AddNodes, AddReferences, DeleteNodes, DeleteReferences
• Method: Call
• Subscription: CreateSubscription, ModifySubscription, SetPublishingMode, Publish, Republish, DeleteSubscriptions, TransferSubscriptions
• MonitoredItem: CreateMonitoredItems, ModifyMonitoredItems, SetMonitoringMode, SetTriggering, DeleteMonitoredItems
• Discovery: FindServers, FindServersOnNetwork, GetEndpoints, RegisterServer, RegisterServer2
• Convenience: ReadValue, ReadValues, WriteValue, BrowseAll, CallMethod, ReadNode, Cancel
• Robotics: typed Robot Intent control and missions, paged monitoring, bounded operation/mission waits, and same-session robotics_vision_pick
• Vision: image capture, structured one-shot inference, result monitoring, feedback and frame-graph composition
• MachineTool/WMTP: native monitoring, tools/life, production/jobs, remote files, independent peripheral measurements, records and explicit configuration
• GMS: native equipment/qualification/calibration and result workflows, bounded observations and consented result acknowledgment
• CranesHoists: observed topology and raw measurements with authorized standard speed-limit requests, never physical motion commands
• Industrial companions: asset management, machinery, weighing, pumps, device integration, ISA-95 jobs and relative/global positioning. See the companion guide.
• WoT and xRegistry: explicit asset/registry/version/label operations, bounded events and content transfers, document validation, binding planning and bidirectional WoT/NodeSet conversion. Remote dependencies require both request opt-in and the host's exact HTTPS origin allowlist; bindings are not executed by these document/management profiles.
• GDS and credentials: directory, pull/push certificate lifecycle, KeyCredential/token issuance and refresh, and Part 21 onboarding. Inputs and outputs use authorized secret-store references, never private material.
• General workflows: role/user administration, bounded regular/temporary files, alarms/conditions, historical reads/mutations and schema artifacts.
• PubSub and live WoT: named runtimes with caller ownership, quotas, idle/absolute expiry and network/operation allowlists. WoT execution supports HTTP(S), MQTT, Modbus TCP and OPC UA. Live Kafka remains disabled until its backend can enforce policy on every broker-discovered connection; Kafka configuration and schema tools remain available.

Companion calls preserve server failures, use bounded lists and observations, and never acquire locks or retry commands implicitly. Package upload and result download require OPCUA_MCP_TRANSFER_ROOT; the default streaming byte limit is 64 MiB (OPCUA_MCP_MAX_TRANSFER_BYTES). Paths cannot escape the configured root.

Embedding

The tools also ship as libraries, so an application can offer OPC UA tools to an LLM alongside its own without forking this server:

builder.Services.AddOpcUaMcpCore();

builder.Services.AddMcpServer()
    .WithStdioServerTransport()
    .WithOpcUaMcpFilters()
    .WithOpcUaCoreTools(McpToolProfile.Services)
    .WithTools<MyApplicationTools>();

Package	Tools
OPCFoundation.NetStandard.Opc.Ua.Mcp.Core	Part 4 services, connection, configuration, PKI, NodeSet export
OPCFoundation.NetStandard.Opc.Ua.Mcp.PubSub	PubSub transports, configuration, bridges, SKS, actions, discovery
OPCFoundation.NetStandard.Opc.Ua.Mcp.Diagnostics	UA-TCP capture, decode, replay
OPCFoundation.NetStandard.Opc.Ua.Mcp.PubSub.Diagnostics	PubSub capture, decode
OPCFoundation.NetStandard.Opc.Ua.Mcp.Robotics	Robot Intent control, missions, waits and Vision-guided Pick
OPCFoundation.NetStandard.Opc.Ua.Mcp.Vision	Vision discovery, seeing, inference, feedback and geometry
OPCFoundation.NetStandard.Opc.Ua.Mcp.MachineTool	MachineTool and bundled wireless-peripheral workflows
OPCFoundation.NetStandard.Opc.Ua.Mcp.GMS	GMS systems, results, downloads and observations
OPCFoundation.NetStandard.Opc.Ua.Mcp.CranesHoists	Crane monitoring and authorized limit requests
OPCFoundation.NetStandard.Opc.Ua.Mcp.AMB	Asset management
OPCFoundation.NetStandard.Opc.Ua.Mcp.Machinery	Machine monitoring, process values, energy and results
OPCFoundation.NetStandard.Opc.Ua.Mcp.Scales	Weighing, products and recipes
OPCFoundation.NetStandard.Opc.Ua.Mcp.Pumps	Pump values, supervision and maintenance
OPCFoundation.NetStandard.Opc.Ua.Mcp.Di	Device integration, locking and updates
OPCFoundation.NetStandard.Opc.Ua.Mcp.ISA95	Common objects and V1/V2 job control
OPCFoundation.NetStandard.Opc.Ua.Mcp.Positioning	Spatial frames and coordinate conversion
OPCFoundation.NetStandard.Opc.Ua.Mcp.WotCon	WoT management/documents and separately registered, policy-controlled live bindings
OPCFoundation.NetStandard.Opc.Ua.Mcp.XRegistry	Generic registry/version/label/content operations
OPCFoundation.NetStandard.Opc.Ua.Mcp.Gds	GDS, certificates, credential/token references, onboarding
OPCFoundation.NetStandard.Opc.Ua.Mcp.Workflows	Roles/users, files, alarms and historical access
OPCFoundation.NetStandard.Opc.Ua.Mcp.Schema	Bounded types and XSD/BSD/JSON, PubSub and OpenAPI artifacts

Robotics and CranesHoists libraries remain preview-only, including Debug variants. The other MCP libraries, including Vision, MachineTool and GMS, follow the root release channel and are stable when the root release is stable. WMTP has no separate package/profile. A development root version can still be prerelease. Conformance depends on actual endpoints/providers; GMS's documented undefined Production-statistics CU does not justify advertising that full facet.

Documentation

See the full documentation.