Skip to main content
Glama
Sign In
OPC UA MCP Server

OPC UA MCP Server

by IndustriAgents
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to OPC UA MCP Server

No user-submitted related servers found.

    Related Servers

    • opcua-mcp

      mwieczorkiewicz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to read, write, browse, search, and subscribe to live data on OPC-UA industrial automation servers, with caching, discovery index, and support for stdio or HTTP transports.
      5
      MIT

    • OPC UA MCP Server

      intigration
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI agents to OPC UA-enabled industrial systems for real-time monitoring and control of operational data. It enables users to read, write, and browse industrial device nodes through natural language interactions.
      MIT

    • opcua-gateway

      IndusNeo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover, browse, read, search, and safely write OPC UA industrial device data within controlled edge networks, with guarded two-phase writes and evidence-based root-cause diagnostics.
      1
      Apache 2.0

    • Octopus MCP Server

      JulieMorozov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to inspect, query, and diagnose issues within an Octopus instance, and to create releases, deploy them to environments and tenants, and run runbooks. Connects via stdio with API key or short-lived token auth, offering selectable toolsets, a read-only mode, and a structured REST backstop.
      453 npm
      MIT

    • OT-AIops

      industrial-aiops
      A
      license
      B
      quality
      A
      maintenance
      Provides AI agents with safe, governed read access to industrial control systems (OPC-UA, Modbus, S7, Mitsubishi, MTConnect, MQTT/Sparkplug) plus cross-protocol diagnostics for troubleshooting data breaks, alarm floods, and unhealthy tags.
      156
      9
      MIT
    • Proxus Industrial MCP Server

      Proxus Industrial MCP Serverofficial

      proxus-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect industrial devices read-only over Modbus TCP and OPC UA, including reading and watching values, browsing nodes, decoding registers, and diagnosing connection issues without any write capability.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target clearly different operations: browsing vs current reads vs history vs live data-change subscriptions vs live events vs alarm listing. The closest pairs are read_events/read_event_history and subscribe_events/subscribe_opcua_nodes, whose names are similar but whose descriptions clearly separate live buffering from archived retrieval and event streams from data-change streams. Slight ambiguity remains from those parallel names, but the descriptions prevent likely misselection.

    Naming Consistency4/5

    All names follow a snake_case verb_noun pattern, which is readable and predictable. The main inconsistency is the optional 'opcua' qualifier: read_opcua_nodes, browse_opcua_nodes, read_opcua_history, subscribe_opcua_nodes, and unsubscribe_opcua_nodes use it, while read_event_history, subscribe_events, read_events, list_subscriptions, and list_active_alarms do not. This is a minor deviation rather than a chaotic naming scheme.

    Tool Count5/5

    At 11 tools, the set is well within a reasonable range for an OPC UA monitoring and browsing server. Each tool covers a distinct capability: status, browse, current read, historical read, data-change subscription lifecycle, event subscription/read, event history, active alarms, and subscription listing. No tool appears redundant or purely filler.

    Completeness3/5

    The read/monitoring surface is fairly complete: browse, current values, historical values, live data changes, event buffering, event history, alarms, and server capability discovery are all present. However, core OPC UA write operations such as writing node values or calling methods are absent, and alarm acknowledgement is not exposed even though alarm listing is. There is also a reference to an 'act_on_alarm' tool in the browse description that is not present in the tool set, indicating a notable surface gap.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources