Log inSubmit server
Ignition MCP logo

Ignition MCP

Connects AI clients to Ignition gateways for tags, history, alarms, projects, gateway administration, and Perspective.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Ignition MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ignition-mcp": {
      "command": "uvx",
      "args": [
        "ignition-mcp"
      ],
      "env": {
        "IGNITION_URL": "YOUR_VALUE_HERE",
        "IGNITION_API_TOKEN": "YOUR_VALUE_HERE",
        "IGNITION_BRIDGE_SECRET": "YOUR_VALUE_HERE",
        "IGNITION_ALLOW_WRITES": "YOUR_VALUE_HERE",
        "IGNITION_TLS_VERIFY": "YOUR_VALUE_HERE",
        "IGNITION_TIMEOUT_S": "YOUR_VALUE_HERE",
        "IGNITION_TAG_WRITE_ALLOWLIST": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx ignition-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 9d ago.

Overview

The ignition-mcp MCP server connects MCP clients to Inductive Automation Ignition gateways through the gateway REST API and an optional WebDev bridge. It exposes tools for tags, history, alarms, projects, gateway administration, databases, and Perspective resources, with 43 tools documented. Reads work by default; mutating operations require explicit configuration and confirmation. Use it when an AI assistant needs structured access to an Ignition 8.3 gateway, especially for live tag data or Perspective deployments.

Use cases

  • Browse and update Ignition tags through an AI client
  • Query tag history and alarm data from a gateway
  • Create, validate, and deploy Perspective views
  • Inspect gateway logs, modules, backups, and performance
  • Manage Ignition projects with guarded write operations

Key features

  • Ignition tag browsing, reading, writing, and configuration transfer
  • History queries and alarm status, journal, and acknowledgement tools
  • Project lifecycle and gateway administration tools
  • Perspective view validation, deployment, and session inspection
  • Optional HMAC-signed WebDev bridge for live gateway scripting access
  • Read-only default with write confirmation and tag allowlisting

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · ignition-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Ignition MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ignition MCP

ignition-mcp is an MCP server that connects AI clients to Inductive Automation Ignition gateways through the REST API and an optional WebDev bridge. Its main tools browse and modify tags, query history and alarms, manage projects and gateway administration, run database queries, and create or deploy Perspective views with guarded writes.

Install it with pipx, uvx, or pip, then configure your MCP client to run the `ignition-mcp` command. Set `IGNITION_URL` and `IGNITION_API_TOKEN`, restart the client, and ask it to run `ignition_diagnose` to check the gateway configuration.

Install the optional `mcp-bridge` WebDev project on the Ignition gateway and set `IGNITION_BRIDGE_SECRET`. Perspective deployment and other mutating actions also require `IGNITION_ALLOW_WRITES=true`; the bridge can be installed through the `bridge_install` tool.

No, writes are disabled by default. Set `IGNITION_ALLOW_WRITES=true`, and mutating tool calls must also include `confirm=true`; tag writes can be further restricted with `IGNITION_TAG_WRITE_ALLOWLIST`.

Yes, the README provides a Claude Desktop configuration using the `ignition-mcp` command and environment variables. Claude Code is also named as a supported client, and the server is intended for MCP clients generally.

Related MCP servers

All in Industrial & IoT All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIgnition MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ignition-mcp?style=directory)](https://allmcps.com/mcp/ignition-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/ignition-mcp"><img src="https://allmcps.com/api/badge/ignition-mcp?style=directory" alt="Ignition MCP on AllMCPs" /></a>