Skip to main content
Glama
purinzan

gx3-mcp-server

Related Servers

Alternatives to gx3-mcp-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Lets AI agents and users analyze Mitsubishi MELSEC .gx3 projects directly, tracing coil conditions, checking device references, comparing program changes, and inspecting ladder logic without opening GX Works3.
      13
      3
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables reading, patching, diffing, packaging, and native compilation of H3U PLC projects offline via MCP, without starting the AutoShop GUI.
      19
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      An MCP server for ABB/Hitachi Energy PCM600 that provides offline IEC 61850 SCL file analysis, .apcmp project archive inspection, ACT logic recovery, and safe read-only drive of the PCM600 CLI for project exports and validation.
      23
      1
      -
    • F
      license
      B
      quality
      D
      maintenance
      Enables AI agents to read and understand local Mendix project structure and logic by connecting directly to the .mpr file via MCP. Allows querying microflows, entities, attributes, and modules in read-only mode without requiring cloud access.
      4
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables offline-first industrial manufacturing workflows by parsing, linting, and drafting FANUC .LS robot programs and analyzing STEP/STP CAD files through MCP tools.
      4
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target clearly distinct analysis tasks (interlock check, dead logic, trace, xref, data flow, lint, device map, alarm map, diff, network map, print, snapshot, replay). The main overlaps are gx3_dead_logic vs gx3_lint and the device-relationship cluster of trace_device/xref_where_used/data_flow, but the detailed descriptions provide enough separation to avoid serious misselection.

    Naming Consistency4/5

    All names share the gx3_ prefix and snake_case style, which creates a strong family identity. The post-prefix portion mixes verb-led names (trace_device, explain_snapshot, replay_capture, run_command) with noun-led report names (dead_logic, device_map, alarm_map, semantic_diff, network_map, ladder_print), a mild convention split that is still readable and predictable.

    Tool Count5/5

    At 15 tools, the count is at the upper boundary of the well-scoped range, and each tool earns its place by addressing a distinct analysis workflow. The command-discovery and escape-hatch tools (gx3_list_commands, gx3_run_command) are justified additions rather than padding for this domain.

    Completeness4/5

    The server covers the core static-analysis, comparison, printing, and offline-capture workflows comprehensively. Minor gaps exist: gx3_ladder_print references a list_sections tool that is not provided as a typed tool, and prerequisite xref/index DBs must be built outside the server, but gx3_run_command or user instructions can work around these.

    Maintenance

    ActivityActive
    ResponsivenessResponsive