Ignition MCP Server

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

Local serverstdioPython

What is the Ignition MCP server?

MCP server for Inductive Automation Ignition: tags, alarms, history, and Perspective. Exposed over MCP by the ignition mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP (Model Context Protocol) server for Inductive Automation Ignition. It gives an AI assistant, Claude Desktop, Claude Code, or any MCP client, structured access to an Ignition gateway: browse and write tags, query history and alarms, manage projects, and deploy full Perspective views.

  • REST plane. — The gateway's native /data/api/v1 API, authenticated with an API key, used
  • Bridge plane. — A small WebDev project (mcp-bridge) you install once on the gateway. It

Configuration

You will need 4 environment variables: IGNITION_URL, IGNITION_API_TOKEN, IGNITION_BRIDGE_SECRET, IGNITION_ALLOW_WRITES. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at ignition-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by jsgorana; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Ignition's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the ignition mcp server does with a few real requests.

How to install the Ignition MCP server

{
  "mcpServers": {
    "ignition": {
      "command": "uvx",
      "args": ["ignition-mcp"],
      "env": {
        "IGNITION_URL": "your-value",
        "IGNITION_API_TOKEN": "your-value",
        "IGNITION_BRIDGE_SECRET": "your-value",
        "IGNITION_ALLOW_WRITES": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
IGNITION_URLEndpoint or connection string the server talks to.Yes
IGNITION_API_TOKENCredential the server authenticates with.Yes
IGNITION_BRIDGE_SECRETCredential the server authenticates with.Yes
IGNITION_ALLOW_WRITESConfiguration value read at startup.Optional

Frequently asked questions

It connects Ignition to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Ignition directly.