Signed Ignition module, 613845 bytes. Requires Ignition 8.3.4 or later, gateway scope.
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.
SHA-256 b09b6fec97a3d4e2d4b28d836e87a9115652aebe784aa622dfa38f7f44b95ea7
Verify it with sha256sum Artek-MCP-2.1.0.modl before you install. The Gateway also verifies the signature and rejects a modified file.
Built by 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.