Skip to main content
Glama
agentthink

io.github.purinzan/gx3-cli-mcp

Related Servers

Alternatives to io.github.purinzan/gx3-cli-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      A
      maintenance
      Provides read-only analysis of Mitsubishi GX Works3 PLC projects via MCP, enabling device tracing, cross-referencing, ladder inspection, linting, and report generation without modifying source projects.
      4
      15
      49 PyPI
      6
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI to operate STEP 7-Micro/WIN SMART via MCP, supporting offline STL/AWL analysis, project inspection, online PLC monitoring (snap7), and engine-injected operations like compile, download, upload, and symbol management through natural language.
      5
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to discover, inspect, edit, rebuild, and save Schneider Electric RemoteConnect and SCADAPack x70 IEC logic projects, including program sections, hardware, variables, and Modbus configuration.
      63
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to Allen-Bradley, Siemens, and CODESYS PLC projects for discovering, asking questions about, analyzing, and proposing code changes, with access to live tag values and version exports under permission-scoped controls.
      -

    TDQS

    A4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool targets a distinct analysis question, and the descriptions are detailed enough to tell device tracing, interlock checking, xref, and lint apart. Minor overlap remains between lint and dead_logic, and between trace_device and xref_where_used, but the use cases are still differentiated.

    Naming Consistency3/5

    All names share the gx3_ prefix and snake_case, but they mix verb-first names like list_commands, trace_device, and run_command with noun-first or noun-only names like device_map, dead_logic, lint, and semantic_diff. The set is readable, but the operation/resource order is not predictable enough for a consistent convention.

    Tool Count5/5

    13 tools is within the ideal scope for a domain-specific analysis server, and every tool maps to a distinct inspection, tracing, linting, mapping, diffing, or rendering task. No obvious filler or redundant tools inflate the count.

    Completeness4/5

    The read-only analysis surface is broad: tracing, xref, data flow, lint, dead logic, device/alarm/network maps, diff, and ladder rendering are all first-class, with an escape hatch for anything else. Minor gaps are that prerequisites like xref/index DB builds are not first-class tools, and a section-list facility is only mentioned in ladder_print rather than exposed as its own tool.