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.
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.
Four more modules from the same engineers. Each one does a job Artek-MCP does not.
Artek-MCP answers when you ask it something. Artekis reads your alarms and history every day on its own, and tells you what it found, with the readings that prove it.
Before you point an AI at a gateway, find out what shape it is in. Pulse runs health and security checks and hands you the report.
Artek-MCP reads your projects. Artek-Designer builds in them: the same assistant adds views and bindings in your open Designer while you watch.
Sending the same tags to a broker or a Unified Namespace? Artek MQTT publishes them straight from the gateway, with nothing extra to run.
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.
They cover gateway health, projects, tags and UDTs, alarms, history, config, Perspective sessions, security, the audit log, EAM and store-and-forward.
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.
It runs on released Ignition, version 8.3.4 or later.
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.
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.
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.
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.
The defaults are the safe settings. This is what they cover and where they stop.
The two are often confused. Artek-MCP ships with the tools already written. IA’s module is a framework for writing your own.
| Artek-MCP | IA MCP Module | Community MCP servers | |
|---|---|---|---|
| Tools on install | 96 | None. You write your own. | Typically 10–20 |
| Where it runs | Inside the gateway | Inside the gateway | A separate process beside it |
| Expose your own functions | Yes, declared per endpoint | Yes, that is its purpose | Varies |
| Status | Released | Early Access | Community projects |
| Cost | $4,000 per gateway, one time; support 20% a year | Free during Early Access; at release, part of IA’s commercial Catalyst Agent module | Mostly free and open source |
| Support | From Artek, with a support plan | None during EA; vendor-backed once released | None |
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.
Before you upgrade
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.
New
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 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.
(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.
license-state change, never one per call.
| Property | Value |
|---|---|
| Version | 2.1.0 |
| File | Artek-MCP.modl · 613845 bytes |
| SHA-256 | b09b6fec97a3d4e2d4b28d836e87a9115652aebe784aa622dfa38f7f44b95ea7 |
| Signing certificate (SHA-1) | 99e472815b3417abab93e1c744c76699c73375d2 |
| Certificate subject | C=US, O=Artek, LLC, CN=Artek, LLC |
| Requires | Ignition 8.3.4 or later · gateway scope |
| Protocol | Model 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.
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.
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 →