@inscada/mcp-server
OfficialRelated Servers
Alternatives to @inscada/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to read, understand, and interact with Ignition SCADA projects and gateways through the Model Context Protocol. Provides structured access to tags, Perspective views, scripts, UDTs, alarm pipelines, and named queries, plus opt-in live tag reads/writes, script execution, and tag history on a running gateway.17MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor and analyze industrial process data from DCS/SCADA systems via MCP protocol, with domain expert knowledge for anomaly detection and recommendations.-
- AlicenseBqualityBmaintenanceExposes a deterministic IoT edge runtime — Modbus/CAN/J1939 acquisition, local rules, alarms, and history — to AI assistants as typed, governed MCP tools. Reads are safe by default; device control stays deny-by-default, explicitly confirmed, and audited.233Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with SkyFoundry SkySpark building automation data via the Model Context Protocol. It allows users to evaluate Axon expressions, perform CRUD operations on records, and manage project functions through a comprehensive suite of 21 tools.MIT

Skyforge MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceConnects AI assistants to SkySpark and Haxall building automation systems by dynamically exposing SkySpark Axon functions as MCP tools. Enables natural language interaction with building data, equipment, and automation functions through real-time tool discovery.5MIT- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that bridges AI assistants with WinCC OA projects, enabling natural language queries for datapoint search, manager management, and CTL script execution.2MIT
TDQS
Scored across 39 tools
Most tools have clearly distinct purposes, with good descriptions. However, 'inscada_api' is a generic catch-all that could be misused if the agent doesn't heed the warning to prefer dedicated tools. The distinction between 'list_variables' and 'search_variables' is clear, and chart tools are well-differentiated.
Naming conventions are mixed: some tools use the 'inscada_' prefix (e.g., 'inscada_get_live_value'), while others like 'list_variables' and 'create_custom_menu' do not. The verb-noun pattern is followed but the prefix inconsistency reduces predictability.
With 39 tools, the set is on the high side. While the SCADA domain justifies a broad surface, some tools like 'inscada_api' could reduce the need for so many dedicated ones. The count feels slightly bloated but still manageable for an agent.
The set covers core operations like CRUD for custom menus and scripts, live data, and charts. However, there are notable gaps: no direct tools for creating or deleting animations or alarms (only 'get_fired_alarms' and 'list_animations'), relying on the generic 'inscada_api' for those.