ignition-mcp-server
Related Servers
Alternatives to ignition-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage and interact with Ignition Gateway 8.3+ through a curated set of tools covering gateway administration, projects, resources, tags, alarms, historian data, and script execution via the REST API.GPL 3.0

@inscada/mcp-serverofficial
AlicenseAqualityDmaintenanceEnables AI assistants to interact with inSCADA systems via the Model Context Protocol, providing 39 tools for live data, alarms, scripts, historical analysis, charts, and more.398 npmMIT- AlicenseAqualityAmaintenanceThe first AI-powered development tool for Ignition SCADA — an MCP server that lets any AI agent read, understand, and interact with your Ignition projects and gateways.1710MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Inductiveautomation's Ignition SCADA/MES platform through its REST API. Provides 45+ tools for gateway management, project operations, backup handling, log analysis, and license activation.37GPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseAqualityAmaintenanceProvides AI agents with safe, governed read access to industrial control systems (OPC-UA, Modbus, S7, Mitsubishi, MTConnect, MQTT/Sparkplug) plus cross-protocol diagnostics for troubleshooting data breaks, alarm floods, and unhealthy tags.1557MIT
TDQS
Scored across 17 tools
Each tool targets a distinct Ignition resource or live-gateway operation; list/get pairs are clearly scoped, and project-file tools like get_tags are differentiated from live tag tools like read_tag and get_history. No two tools appear to do the same thing.
Nearly all tools use snake_case verb_noun (list_views, get_view, execute_script, read_tag). Minor deviations are get_tags instead of the list_* pattern used for most other resources, and the bare ping health check.
17 tools are reasonable for covering tags, providers, views, scripts, UDTs, alarms, named queries, and live gateway operations, but slightly above the ideal 3-15 range.
The surface covers reading and inspecting most Ignition project resource types plus live tag read/write, script execution, and history. Gaps include no create/update/delete for project resources and no direct named-query execution, though execute_script can work around some.