ignition-mcp-server
Related Servers
Alternatives to ignition-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceMCP 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.4339 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.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceMCP 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.37-
- FlicenseBqualityBmaintenanceUniversal 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
Each tool targets a distinct resource or operation. The 'list_' vs 'get_' pattern clearly separates enumeration from detailed retrieval, and runtime operations (read_tag, write_tag, execute_script, get_history) are distinct from static project inspection tools. No overlapping purposes.
All tools use a consistent verb_noun naming convention with underscores (e.g., get_tags, list_views, write_tag). Even 'ping' follows the verb pattern. No mixing of styles or irregular patterns.
17 tools cover both static project exploration (list/get for multiple resource types) and live gateway operations (script execution, history, tag I/O). The scope is well-defined without being overwhelming, and each tool has a clear purpose.
The tool set covers the main Ignition project resources (views, scripts, tags, alarms, queries, UDTs) and critical runtime operations. Minor omissions exist (e.g., no tool to list tag provider properties, no update operations) but are reasonable for a read- and query-focused server.