FreeIgnition® MRI: send us a gateway backup, and our engineers rank every risk in it within five business days.Get yours →
Home / Community / MCP Ignition 8.3 module

MCP lets an AI agent read your Ignition gateway.

Artek-MCP is a signed module that makes your Ignition gateway a Model Context Protocol (MCP) server. Once installed, it gives your MCP client 96 tools for projects, tags, alarms, history, config, security and diagnostics. It remains read-only until you change that setting.

License
$4,000
per gateway, one time
Annual support
20%
of the price paid, per year

Try it free first. Without a key the module runs for Ignition’s two-hour trial, which you can reset from the gateway. After the trial, tool calls need an Artek-MCP license key on that gateway, and the settings page shows the license state. Free evaluation keys are available on request until December 31, 2026. A backup gateway of a redundant pair is half price.

A real gateway: an AI assistant answers a plant question from live tags and history, reads a whole project for your developers, and compares and deploys changes, with writes off until you allow them.

Goes well with Artek-MCP

Once an assistant can read your gateway, here is what to add next.

Four more modules from the same engineers. Each one does a job Artek-MCP does not.

What it is

One signed module that runs inside the gateway.

Artek-MCP is a signed Java module that installs like any other Ignition module. There is no separate server to run, and no tools to write before it is useful.

Where Artek-MCP fits An AI client connects over HTTPS to the Artek-MCP endpoint inside the Ignition gateway, authenticated by an API key or OAuth. A policy layer, read-only by default, decides what each key may reach: projects and views, tags, alarms and history, logs and diagnostics, configuration and databases. Every call is audited. AI client Claude Code, Claude Desktop, Codex or any MCP client Ignition Gateway Artek-MCP MCP endpoint API key or OAuth; rate limits per key Policy read-only by default; allowlist, per-key scopes, redundancy gate Audit log every call, allowed or refused MCP over HTTP Projects and views read; write if allowed Tags, alarms, history browse, query, read Logs and diagnostics windowed queries Config and databases read; DB only if enabled
An AI client reaches the gateway only through Artek-MCP, and only as far as the policy allows.
96 TOOLS

Available at install

They cover gateway health, projects, tags and UDTs, alarms, history, config, Perspective sessions, security, the audit log, EAM and store-and-forward.

IN-GATEWAY

No bridge process

Your MCP client connects over streamable-HTTP MCP directly to /data/artek-mcp/mcp on the gateway. No process runs between the agent and the gateway.

8.3.4+

Ignition 8.3.4 and later

It runs on released Ignition, version 8.3.4 or later.

What you can do with it

An agent can reach three areas, and two of them are off by default.

The 96 built-in tools cover the gateway itself. Two optional providers extend that reach. Both ship disabled, and both still work while the server is read-only.

INSPECT

The gateway itself

Projects and resources, tags and UDTs, alarms and journals, tag history, config, Perspective sessions, security inventory, audit log, logs and diagnostics. No setup is required beyond the API key, and no code.

SQL

Your plant database

With the db provider enabled, an agent can answer questions directly from the data. It can run ad-hoc SELECTs against connections you name one at a time, or run your existing Named Queries. Nothing is exposed until you name it.

YOUR CODE

Functions you choose to expose

Declare a project library function as an endpoint and it becomes its own MCP tool, with its own description and argument schema. Arbitrary code cannot be run. The agent can call only what you declared.

The third provider is tightly scoped. Exposing mes.getActiveWorkOrder as a tool does not give an agent a Python prompt on your gateway. It gives it that one function, with the arguments you declared, running in the project scope you chose. Everything else stays out of reach.

Security model

It ships read-only, and read-only has limits.

The defaults are the safe settings. This is what they cover and where they stop.

  • Write tools ship disabled. readOnly is on by default, and the allowlist blocks everything until you add to it.
  • Every request is authenticated. It needs an API key, or an OAuth bearer token if you turn OAuth on.
  • Every call is logged on the gateway.
  • Read-only access is still broad. A valid key can read project source, tag values, audit records and the user list. Treat every key like a gateway credential.
  • Enabling writes grants admin-level access. With read-only off, a caller can write resources that the gateway then runs.
  • No telemetry. The module does not call home. It connects only to endpoints you configure.
How it compares

It does a different job from Inductive Automation’s MCP module.

The two are often confused. Artek-MCP ships with the tools already written. IA’s module is a framework for writing your own.

 Artek-MCPIA MCP ModuleCommunity MCP servers
Tools on install96None. You write your own.Typically 10–20
Where it runsInside the gatewayInside the gatewayA separate process beside it
Expose your own functionsYes, declared per endpointYes, that is its purposeVaries
StatusReleasedEarly AccessCommunity projects
Cost$4,000 per gateway, one time; support 20% a yearFree during Early Access; at release, part of IA’s commercial Catalyst Agent moduleMostly free and open source
SupportFrom Artek, with a support planNone during EA; vendor-backed once releasedNone

To publish a small set of your own tools to an LLM, use IA’s module, which is built for that. Once it ships inside the commercial Catalyst Agent module (general release February 2027), it will include vendor support. Artek-MCP is supported by Artek under a support plan.

For an agent that can already read your gateway (every project resource, every tag, the alarm journal, the audit log and the logs) without writing a tool first, use Artek-MCP. It can also expose your own functions.

The two are not exclusive. Both can be installed on the same gateway.

This comparison is as of October 2026, taken from Inductive Automation’s ICC 2026 announcements and their Early Access forum thread. Details change, so confirm against their forum before making a decision.

Release notes

What’s new in v2.1.0.

  • v2.1.0 — licensed: a key per gateway, beyond the Ignition trial. Part of the shared 2.1 release that every Artek module now carries (they move together each release from here; the last number is kept for a fix to a single module). For Artek-MCP it is not a renumber: a gateway that ran it free now needs a key once its trial ends. Licensed exactly as Artekis is (the manual section "Licensing & trial").

Before you upgrade

  • Get an Artek-MCP license key for each gateway, each node of a redundant pair included.

Without one the module runs in the Ignition trial; when the trial ends, every tool call except mcp_status is refused until a key is activated under Platform → Licensing or the trial is reset there. Free on Maker Edition.

  • The license agreement is unchanged, so licenseAgreementHash stays 1399815467.
  • Nothing else changes. Settings, keys, tool names and arguments are as in v2.0.1.

New

  • Every tool call — over the MCP endpoint and over Gateway Network federation — passes a license

check before any other gate. When the license does not allow tool calls, the call is refused with a policy error naming the license state and what to do, carrying a data.license block. mcp_status, tools/list, initialize, the prompts and the module's own artek-mcp://status and artek-mcp://tools resources keep working; resources/read of the gateway-data resources is refused like a tool call.

  • The license is read on every call, so activating a key or resetting the trial takes effect on

the next call, with no restart. A subscription key gets 30 days' grace after it expires, with a warning; an evaluation key stops at its date.

  • mcp_status, artek-mcp://status and the authenticated GET /status carry a license block

(state, expiry, whether tools are allowed); the settings page's Status card shows the state and expiry, and a warning when tools are refused or the key is in grace.

  • Refusals are audited one per call, like every other refusal; the gateway log gets one line per

license-state change, never one per call.

Verify what you downloaded

Check the file before you install it.

PropertyValue
Version2.1.0
FileArtek-MCP.modl · 613845 bytes
SHA-256b09b6fec97a3d4e2d4b28d836e87a9115652aebe784aa622dfa38f7f44b95ea7
Signing certificate (SHA-1)99e472815b3417abab93e1c744c76699c73375d2
Certificate subjectC=US, O=Artek, LLC, CN=Artek, LLC
RequiresIgnition 8.3.4 or later · gateway scope
ProtocolModel Context Protocol · revision 2025-06-18 (also accepts 2025-03-26, 2024-11-05)

Run sha256sum Artek-MCP-2.1.0.modl and compare the result to the SHA-256 above. The Gateway also verifies the signature and rejects a modified file.

Install

Installation takes five steps.

  1. Download the .modl and verify its SHA-256.
  2. In the Gateway, open Platform, then System, then Modules. Choose Install or Upgrade Module and upload the file.
  3. Read and accept the End User License Agreement the Gateway shows you. The module won’t run until you do.
  4. Open the module's settings page, generate an API key, and point your MCP client at /data/artek-mcp/mcp.
  5. Before the two-hour trial ends, activate your Artek-MCP license key under Platform, then Licensing. It takes effect on the next call, with no restart.

If you install it headlessly through modules.json, the entry needs a licenseAgreementHash (the CRC32 of license.html inside the modl). Without it the gateway stalls in commissioning.

Upgrading from 1.49 or earlier? Version numbering restarted at 1.0.0 when the module moved to the Artek, LLC signing certificate, so 1.0.0 and every version after it are newer than 1.49. Install the new build over the old one: the module ID is the same, so your configuration is kept. The Gateway shows the version going down and asks you once to accept the new certificate.

Let's talk

We can help you deploy it on a production gateway.

A license and support plan cover the module. Deciding what an agent should see on your system, and configuring it, is engineering work we quote separately. Call us at the number below and we will connect you with the right engineer.

Get in touch →
(877) 318-0200
Inductive Automation Premier Integrator badge