Artek-MCP is a free module that makes your Ignition gateway a Model Context Protocol (MCP) server. Once installed, it gives your MCP client 95 tools for projects, tags, alarms, history, config, security and diagnostics. It remains read-only until you change that setting.
The module is free, unsupported and provided AS IS. The terms are shown before you download, and the Gateway displays the full license at install.
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 95 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 | 95 | 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 | Free, unsupported | Free during EA; slated for the paid Enterprise Integration Solution Suite | Mostly free and open source |
| Support | None (AS IS) | 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 Enterprise Integration Solution Suite it will include vendor support, which we do not offer.
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 September 2026, taken from Inductive Automation’s Early Access announcement and their forum thread. Early Access details change, so confirm against their forum before making a decision.
| Property | Value |
|---|---|
| Version | 1.49.0 |
| File | Artek-MCP.modl · 520250 bytes |
| SHA-256 | db5c86d41bf452038e827412a49001fc2b3bc20e09e658498bf38b5742f9332e |
| Signing certificate (SHA-1) | 8a507cf6ad4f4d16fb40f411a4dea2faa54d6025 |
| Certificate subject | C=US, O=Artek Integrated Solutions, OU=Engineering, CN=Artek Integrated Solutions |
| 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-1.49.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.
The module is free and unsupported. Deciding what an agent should see on your system, and configuring it, is paid engineering work. Call us at the number below and we will connect you with the right engineer.
Get in touch →