Provides integration with Inductiveautomation's Ignition SCADA/MES platform through its REST API, enabling AI assistants to manage gateway operations, handle backups, monitor logs, manage modules and projects, and perform license activation tasks.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ignition MCP Servershow me the current gateway status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ignition-mcp
A Model Context Protocol (MCP) server that gives AI assistants a curated, developer-oriented interface to the Ignition Gateway REST API.
Built on FastMCP with 37 hand-crafted tools covering gateway management, projects, resources, tag providers, tags, alarms, tag history, and script execution.
Tools
Category | Tools | Backend |
Gateway (6) |
| Native REST |
Projects (8) |
| Native REST |
Project Resources (4) |
| Native REST |
Designers (1) |
| Native REST |
Tag Providers (4) |
| Native REST |
Tag Browse (1) |
| Native REST |
Tag Values (2) |
| WebDev |
Tag Config (6) |
| WebDev |
Alarms (3) |
| WebDev |
Historian (1) |
| WebDev |
Script Execution (1) |
| WebDev |
Requirements
Python 3.10+
Ignition Gateway 8.3+ with REST API enabled
Gateway credentials (API key preferred) or basic auth
Setup
Environment Variables
All environment variables are prefixed with IGNITION_MCP_:
Variable | Default | Description |
|
| Gateway base URL |
| (empty) | API key auth (preferred over basic auth) |
|
| Basic auth username |
|
| Basic auth password |
|
| Set |
| (empty) | WebDev path for |
| (empty) | WebDev path for tag CRUD |
| (empty) | WebDev path for alarm tools |
| (empty) | WebDev path for |
| (empty) | WebDev path for |
|
| Set |
|
| MCP server bind host |
|
| MCP server port |
Running
Client Configuration
Claude Code (.mcp.json)
Claude Desktop (claude_desktop_config.json)
WebDev Prerequisite (tag values, alarms, history, script execution)
Several tools require WebDev module scripts deployed on the target Ignition gateway.
The native REST API (/data/api/v1/) only covers configuration — it does not support
runtime tag reads/writes, alarm queries, historian, or script execution.
Tools that require WebDev endpoints:
Tag values:
read_tags,write_tag→IGNITION_MCP_WEBDEV_TAG_ENDPOINTTag CRUD:
get_tag_config,create_tags,edit_tags,delete_tags,list_udt_types,get_udt_definition→IGNITION_MCP_WEBDEV_TAG_CONFIG_ENDPOINTAlarms:
get_active_alarms,get_alarm_history,acknowledge_alarms→IGNITION_MCP_WEBDEV_ALARM_ENDPOINTHistorian:
get_tag_history→IGNITION_MCP_WEBDEV_TAG_HISTORY_ENDPOINTScript execution:
run_gateway_script→IGNITION_MCP_WEBDEV_SCRIPT_EXEC_ENDPOINT+IGNITION_MCP_ENABLE_SCRIPT_EXECUTION=true
If a WebDev endpoint is not configured, the relevant tools return a clear error with setup instructions. See docs/webdev-setup.md for gateway-side deployment scripts.
Testing
Architecture
License
MIT