# ignition-mcp [Health: Active]

**Category:** 🏭 Industrial & IoT  
**Repository:** https://github.com/jsgorana/ignition-mcp  
**GitHub Stars:** 1  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ignition-mcp

## Description
MCP server for Inductive Automation Ignition: tags, alarms, history, and Perspective

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "ignition-mcp": {
    "command": "uvx",
    "args": ["ignition-mcp"],
    "env": {
      "IGNITION_URL": "",
      "IGNITION_API_TOKEN": "",
      "IGNITION_BRIDGE_SECRET": "",
      "IGNITION_ALLOW_WRITES": "",
      "IGNITION_TLS_VERIFY": "",
      "IGNITION_TIMEOUT_S": "",
      "IGNITION_TAG_WRITE_ALLOWLIST": ""
    }
  }
}
```

**Requires environment variables:** `IGNITION_URL`, `IGNITION_API_TOKEN`, `IGNITION_BRIDGE_SECRET`, `IGNITION_ALLOW_WRITES`, `IGNITION_TLS_VERIFY`, `IGNITION_TIMEOUT_S`, `IGNITION_TAG_WRITE_ALLOWLIST` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What ignition-mcp MCP server does

The ignition-mcp MCP server gives an MCP client structured access to an Inductive Automation Ignition gateway. It is tested against Ignition 8.3 and provides 43 tools covering diagnostics, tags, history, alarms, projects, gateway administration, databases, and Perspective.

Tag operations include browsing, reading, writing, creating, and importing or exporting tag configuration. Other tools query historical values, inspect alarm status and journals, acknowledge alarms, and run named or direct database queries. Project and gateway tools cover project lifecycle actions, gateway modules, logs, backups, performance information, configuration resources, and trial status.

Perspective support includes creating a project foundation, listing and editing views, validating view definitions, managing page configuration and styles, reading session properties, and listing sessions. Two MCP resources provide the view schema and templates for flex, coordinate, and tag-bound dashboard views.

## How it works

The ignition-mcp MCP server uses two connection paths. The REST path calls Ignition's native `/data/api/v1` endpoints with an API key. It handles projects, gateway configuration, modules, logs, backups, and Perspective session diagnostics.

The bridge path uses a WebDev project named `mcp-bridge`, installed on the gateway. It exposes selected Ignition scripting and project file operations through HMAC-signed HTTP requests. Bridge access supports live tag values, tag history, alarms, database operations, and Perspective-related project work that the native REST API does not provide. Tools that need the bridge report a clear unavailable state when it has not been installed. `ignition_diagnose` checks the current configuration and identifies missing setup.

For Perspective authoring, the intended sequence is to read the schema resource, start from a template, validate the view, and then deploy it with the upsert tool. Deployment validates again, writes the view, and triggers a project scan.

## Setup and configuration

Install the package with `pipx install ignition-mcp`, `uvx ignition-mcp`, or `pip install ignition-mcp`. Configure the MCP client command as `ignition-mcp` and provide `IGNITION_URL` plus `IGNITION_API_TOKEN`. The token is an Ignition API key in `name:secret` form, and its security level needs gateway read/write permission in Ignition.

Set `IGNITION_BRIDGE_SECRET` to enable bridge tools. Installing the bridge also requires `IGNITION_ALLOW_WRITES=true`; the bridge can then be installed through `bridge_install`. Optional settings control TLS verification, request timeout, and the tag-write allowlist. TLS verification defaults to enabled, the timeout defaults to 30 seconds, and the write allowlist accepts comma-separated glob patterns.

## Tools and capabilities

The documented tool groups are:

- Diagnostics: gateway checks, information, trial status, and trial reset
- Tags: browse, read, write, create, import, and export configuration
- History and alarms: query history, list providers, inspect status and journals, and acknowledge alarms
- Projects: list, inspect, create, delete, import, export, and scan
- Perspective: bootstrap projects, manage views, validate definitions, configure pages and styles, and inspect sessions
- Gateway administration: modules, logs, logger levels, backups, performance, and configuration resources
- Database and bridge: run database queries or named queries, install the bridge, and inspect bridge status

## Limitations and notes

The server is read-only unless `IGNITION_ALLOW_WRITES=true` is set and a mutating call includes `confirm=true`. Destructive project or view actions require the exact resource name to be supplied again. Tag writes can be restricted with path glob patterns.

REST mutations retain the API key identity in Ignition's audit log, while bridge mutations use the `mcp-bridge` logger. Secrets are not logged or returned. Bridge file operations are limited to the `data/projects/` tree. The project is community-built and is not affiliated with Inductive Automation; write-enabled tools should be tested against a non-production gateway first.

_Full upstream README: https://allmcps.com/mcp/ignition-mcp/readme_