Skip to main content
Glama
Maxkrempl

MCP PLC Core

by Maxkrempl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to MCP PLC Core

No user-submitted related servers found.

    Related Servers

    • industrial-mcp

      zhiningsun
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI models read and control industrial devices via standardized protocols like Modbus, OPC UA, and MQTT, with simulation and real hardware modes.
      4
      MIT

    • plc-mcp-server

      OlubunmiAde
      A
      license
      A
      quality
      F
      maintenance
      MCP server for industrial PLC integration, enabling AI to read tags, monitor alarms, and interact with Allen-Bradley ControlLogix PLCs via natural language.
      9
      MIT

    • x402-industrial-mcp

      xXbrucyjucyXx
      A
      license
      Not graded
      quality
      C
      maintenance
      The first and only MCP server for PLC (Programmable Logic Controller) intelligence. Give any AI agent direct access to industrial automation data — ladder logic, tag databases, cross-references, fault root cause analysis, and sequence blockers
      MIT

    • wago-plc-mcp-server

      WagoAlex
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that connects WAGO PLCs to LLM agents via the WDx/WDA REST API, enabling AI assistants to read sensor values, change configuration, trigger firmware updates, or monitor entire PLC fleets without custom code.
      55 PyPI
      3
      -

    • plc-mcp

      Denisijcu
      F
      license
      Not graded
      quality
      C
      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.
      -
    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

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Tools are mostly distinct: read_sensor, get_alarms, get_status, get_setpoints, and write_setpoint each target a specific domain area. The main overlap is get_all, which subsumes the individual getters, potentially confusing an agent about whether to call it or individual tools, though descriptions make the distinction reasonably clear.

    Naming Consistency4/5

    Naming follows a consistent verb_noun pattern: read_sensor, get_alarms, get_status, get_setpoints, write_setpoint, get_all. Minor inconsistency exists with 'read' vs 'get' for data retrieval (read_sensor uses read while others use get), but this is a small deviation and the pattern is otherwise uniform.

    Tool Count5/5

    Six tools is a well-scoped set for a PLC control server, covering the essential read and write operations without bloat. Each tool serves a clear purpose, and the count is appropriate for the domain.

    Completeness4/5

    The surface covers reading sensors, alarms, status, and setpoints, plus writing setpoints with safety validation. Notably missing are operations for controlling outputs (writing discrete/analog output values) and acknowledging alarms, which are common PLC tasks. However, get_all consolidates reads, and setpoint writing is the safety-relevant write path.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources