ignition-mcp-server
Related Servers
Alternatives to ignition-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceMCP server for Inductive Automation Ignition, enabling AI assistants to browse and write tags, query history and alarms, manage projects, and deploy Perspective views through natural language.4365 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceThe 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 blockersMIT
- AlicenseAqualityCmaintenanceAn MCP server that provides AI assistants with real-time access to Inductive Automation Ignition documentation, enabling accurate answers on Ignition-specific topics by searching live docs and fetching full pages.3MIT
- AlicenseNot gradedqualityBmaintenanceA multi-target MCP server that gives AI clients read and, when permitted, write access to Ignition 8.3 gateways across configuration, project exports, live runtime values, and an offline Ignition reference corpus. It enables browsing, explaining, diagnosing, and gated changes to gateway configuration, projects, tags, and live values through 81 tools with per-target credentials and write policies.4Apache 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server that connects AI assistants to Siemens TIA Portal via the Openness API. AI-assisted PLC programming, project management, hardware configuration, cross-reference analysis, and deployment. 19 tools, 230 actions.46-
- FlicenseBqualityCmaintenanceUniversal 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-
TDQS
Scored across 17 tools
Most tools target distinct resources (alarms, views, scripts, UDTs, queries, tags) and separate project inspection from live gateway operations. There is minor potential overlap between get_tags and read_tag, and get_udt can return all UDTs when no name is given, but descriptions generally clarify the boundaries.
Tool names consistently use snake_case with predictable verb_noun forms such as list_alarms, get_view, list_named_queries, read_tag, and write_tag. The only non-resource verb is ping, which is a standard health-check name and does not break the overall pattern.
With 17 tools, the server is slightly above the ideal 3–15 range, but the breadth is justified by covering several distinct Ignition resource families plus live gateway operations. Each tool has a clear role, so the count feels reasonable rather than bloated.
The set provides strong read/list coverage for alarms, tags, views, scripts, UDTs, and named queries, plus live read/write/script/history operations. However, there are no create, update, or delete tools for project resources, which leaves notable lifecycle gaps for an Ignition management surface.