How do I use ignition-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ignition-mcp what alarms are currently active on the production line?" 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

by asemenovarglass

Overview Schema Source Related Servers Discussions Admin

Remote

ignition-mcp

Documentation · Releases · Issues

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)	`get_gateway_info`, `get_module_health`, `get_gateway_logs`, `get_database_connections`, `get_opc_connections`, `get_system_metrics`	Native REST
Projects (8)	`list_projects`, `get_project`, `create_project`, `delete_project`, `copy_project`, `rename_project`, `export_project`, `import_project`	Native REST
Project Resources (4)	`list_project_resources`, `get_project_resource`, `set_project_resource`, `delete_project_resource`	Native REST
Designers (1)	`list_designers`	Native REST
Tag Providers (4)	`list_tag_providers`, `get_tag_provider`, `create_tag_provider`, `delete_tag_provider`	Native REST
Tag Browse (1)	`browse_tags`	Native REST
Tag Values (2)	`read_tags`, `write_tag`	WebDev
Tag Config (6)	`get_tag_config`, `create_tags`, `edit_tags`, `delete_tags`, `list_udt_types`, `get_udt_definition`	WebDev
Alarms (3)	`get_active_alarms`, `get_alarm_history`, `acknowledge_alarms`	WebDev
Historian (1)	`get_tag_history`	WebDev
Script Execution (1)	`run_gateway_script` (disabled by default)	WebDev

Related MCP server: GoClaw MCP Server

Requirements

Python 3.10+
Ignition Gateway 8.3+ with REST API enabled
Gateway credentials (API key preferred) or basic auth

Setup

# Install
uv sync

# Configure
cp .env.example .env
# Edit .env with your gateway URL and credentials

Environment Variables

All environment variables are prefixed with IGNITION_MCP_:

Variable	Default	Description
`IGNITION_MCP_IGNITION_GATEWAY_URL`	`http://localhost:8088`	Gateway base URL
`IGNITION_MCP_IGNITION_API_KEY`	(empty)	API key auth (preferred over basic auth)
`IGNITION_MCP_IGNITION_USERNAME`	`admin`	Basic auth username
`IGNITION_MCP_IGNITION_PASSWORD`	`password`	Basic auth password
`IGNITION_MCP_SSL_VERIFY`	`true`	Verify TLS certificates. For a private CA, set `SSL_CERT_FILE` to a CA bundle or `SSL_CERT_DIR` to a certificate directory. `false` is for isolated local development only
`IGNITION_MCP_WEBDEV_TAG_ENDPOINT`	(empty)	WebDev path for `read_tags`/`write_tag`
`IGNITION_MCP_WEBDEV_TAG_CONFIG_ENDPOINT`	(empty)	WebDev path for tag CRUD
`IGNITION_MCP_WEBDEV_ALARM_ENDPOINT`	(empty)	WebDev path for alarm tools
`IGNITION_MCP_WEBDEV_TAG_HISTORY_ENDPOINT`	(empty)	WebDev path for `get_tag_history`
`IGNITION_MCP_WEBDEV_SCRIPT_EXEC_ENDPOINT`	(empty)	WebDev path for `run_gateway_script`
`IGNITION_MCP_ENABLE_SCRIPT_EXECUTION`	`false`	Set `true` to enable `run_gateway_script`
`IGNITION_MCP_SERVER_HOST`	`127.0.0.1`	MCP server bind host
`IGNITION_MCP_SERVER_PORT`	`8007`	MCP server port

Running

# Streamable HTTP (default) — http://localhost:8007/mcp
uv run python mcp_server.py

# stdio transport (for Claude Desktop subprocess mode)
uv run python mcp_server.py --transport stdio

Client configuration

For an HTTP MCP client, use http://127.0.0.1:8007/mcp after starting the server.

For a client that launches a stdio subprocess, use uv as the executable with these arguments:

["--directory", "/absolute/path/to/ignition-mcp", "run", "python", "mcp_server.py", "--transport", "stdio"]

Replace the path with your checkout. See the quickstart for the first request and configuration for settings.

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_ENDPOINT
Tag CRUD: get_tag_config, create_tags, edit_tags, delete_tags, list_udt_types, get_udt_definition → IGNITION_MCP_WEBDEV_TAG_CONFIG_ENDPOINT
Alarms: get_active_alarms, get_alarm_history, acknowledge_alarms → IGNITION_MCP_WEBDEV_ALARM_ENDPOINT
Historian: get_tag_history → IGNITION_MCP_WEBDEV_TAG_HISTORY_ENDPOINT
Script 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

# Unit tests (no live gateway needed)
uv run pytest tests/ -v

# Integration tests (requires running Ignition gateway)
RUN_LIVE_GATEWAY_TESTS=1 uv run pytest tests/test_integration.py -v

Architecture

mcp_server.py                      # FastMCP entry point, lifespan, arg parsing
src/ignition_mcp/
    config.py                      # Pydantic Settings (IGNITION_MCP_ prefix)
    ignition_client.py             # Async HTTP client (httpx) for Gateway REST + WebDev
    tools/
        __init__.py                # register_all(mcp) — calls each module
        gateway.py                 # info, health, logs, connections, metrics
        projects.py                # project CRUD + export/import
        resources.py               # project resource CRUD (native REST)
        designers.py               # list_designers
        tag_providers.py           # tag provider CRUD
        tags.py                    # browse + read/write + CRUD via WebDev
        alarms.py                  # alarm query + ack (WebDev)
        historian.py               # tag history (WebDev)
        execution.py               # run_gateway_script (off by default)
tests/
    conftest.py                    # Shared fixtures
    test_client.py                 # IgnitionClient unit tests (mocked httpx)
    test_tools.py                  # Tool logic unit tests (mocked client)
    test_integration.py            # Live gateway tests (skipped by default)
docs/
    webdev-setup.md                # WebDev script deployment guide
    api-reference.md               # Full tool reference

License

MIT

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

Sugra API A
ai.sugra
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
Search Open Data Data Platforms
1122
mcp-serverOAuth
com.make
Give your AI agents the tools to build, manage, and run automation workflows.
App Automation Developer Tools Workplace & Productivity
2
nexusOAuth
com.civic
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Agent Orchestration Developer Tools App Automation
2
Energy AT IT
com.energyatit.app
Protocol-native energy infrastructure orchestration for AI data centers. Provides 46 MCP tools across 8 grid protocols (IEC-61850, DNP3, Modbus, OCPP, OpenADR, IEEE 2030.5, IEC 60870-5-104, ICCP) with 5 core API primitives: connect, dispatch, settle, comply, and intel. Enables AI agents to programmatically interact with substations, grid interfaces, and energy assets for real-time workload-grid coordination.
Cloud Platforms Agent Orchestration Virtualization
2

Related MCP Servers

Ignition MCP Server
Monitoring Developer Tools App Automation
WhiskeyHouse
A
license
Not graded
quality
D
maintenance
Enables 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.
Updated 6 days ago (2026-09-14 10:41 UTC)
35
GPL 3.0
GoClaw MCP Server
Agent Orchestration Developer Tools Autonomous Agents
nextlevelbuilder
F
license
B
quality
F
maintenance
Enables AI assistants to manage GoClaw AI gateway infrastructure through a comprehensive suite of 66 tools for managing agents, sessions, and configurations. It provides real-time gateway context and guided workflows with enterprise-grade security features like audit logging and secret scrubbing.
Updated 6 months ago (2026-03-15 05:08 UTC)
66
10
-
@inscada/mcp-serverofficial
Monitoring Data Visualization Search
inscada-app
A
license
A
quality
D
maintenance
Enables 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.
Updated 5 months ago (2026-04-06 11:34 UTC)
39
41 npm
MIT
ignition-mcp-server
Developer Tools Code Execution
Nodeblue-AI
A
license
A
quality
C
maintenance
The 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.
Updated a month ago (2026-08-13 20:13 UTC)
17
10
MIT

ignition-mcp

Tools

Requirements

Setup

Environment Variables

Running

Client configuration

WebDev Prerequisite (tag values, alarms, history, script execution)

Testing

Architecture

License

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Ignition MCP Server

GoClaw MCP Server

@inscada/mcp-serverofficial

ignition-mcp-server