Skip to main content
Glama
brayangcastro

industrial-mcp

Related Servers

Alternatives to industrial-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      3
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      Universal MCP server for industrial PLC communication, enabling AI agents to read sensors, alarms, status, setpoints, and write setpoints via adapters for Modbus, S7, or custom PLCs.
      6
      -
    • 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.
      -
    • 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
    • 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that connects Claude Code to your work environment through auditable tools for file operations, API calls, and command execution, with safety gates and configuration.
      -

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: plants, silos, thermometry, motors, alerts, and motor actions. The only possible overlap is between list_silos and get_silo_thermometry, but one lists silos and the other retrieves data for a specific silo, so there is no ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_plants, list_silos, list_motors, get_active_alerts, get_silo_thermometry, trigger_motor_action. The verbs are clear and the style is uniformly snake_case, making the set predictable and easy to navigate.

    Tool Count5/5

    With 6 tools, the server is well-scoped for industrial monitoring and control. Each tool serves a clear purpose without excessive overlap or unnecessary additions, and the count is neither too thin nor too heavy for the domain.

    Completeness4/5

    The tool set covers the core workflows: listing assets, retrieving detailed sensor data, checking alerts, and issuing motor control commands with safety checks. Minor gaps exist, such as no dedicated tool for getting a single motor's detailed status or acknowledging alerts, but these do not critically hinder agent operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues