Skip to main content
Glama

Related Servers

Alternatives to plc-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Connect AI assistants to industrial OPC UA systems. Browse nodes, read live data and history, and monitor subscriptions, events and alarms. Runs locally over stdio in read-only mode by default.
      11
      34
      MIT
    • 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects a local LLM to an industrial PLC via Modbus TCP, enabling process reading, alarm correlation, and safe diagnosis with restricted write access through an allowlist. Includes a simulated PLC with real physics for local testing.
      -
    • A
      license
      B
      quality
      B
      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.
      157
      13
      MIT
    • A
      license
      Not graded
      quality
      C
      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

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    The read surface is cleanly split: lister_variables lists metadata, lire_variable/lire_variables read values, and historique pulls time series; the singular/plural pair is spelled out well in the descriptions. The only real overlap is between lister_alarmes and journal_evenements, which both surface alarm chronologies (the latter adds stops and causes), so an agent could occasionally pick the wrong one. The three-step write flow (ecrire/confirmer/annuler) is explicitly delineated.

    Naming Consistency4/5

    Eight of ten tools use a verb_noun French pattern (lister_*, lire_*, ecrire_*, confirmer_*, annuler_*, generer_documentation) with consistent lowercase snake_case. The exceptions are 'historique' and 'journal_evenements', which are noun-only names and break the verb-first convention. The style is otherwise uniform and readable.

    Tool Count5/5

    Ten tools is well within a comfortable scope for a PLC monitoring/control server. Each tool earns its place: the split write-offer/confirm/cancel trio is justified by the safety requirement of operator confirmation, and no tool is redundant filler.

    Completeness4/5

    The surface covers listing, single and batch reads, history, alarm/event timelines, a guarded write lifecycle, and documentation generation — a solid lifecycle for the domain. Gaps remain: no alarm acknowledgement/reset, no batch write preparation, and no live subscription or polling for value changes. Agents can work around these but they are real omissions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues