Skip to content

Artek-MCP

Artek-MCP turns your Ignition gateway into a Model Context Protocol (MCP) server. Once it is installed, an MCP client (an AI agent such as Claude Code, or any other MCP-capable tool) can read your projects, tags, alarms, history, configuration, security inventory, logs and diagnostics directly from the gateway, with no tools to write first.

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.

It ships read-only. Tools that change gateway state are blocked until an administrator deliberately turns writes on and names what may be changed.

What it is

  • One signed module that runs inside the gateway. Artek-MCP installs like any other Ignition module (module id com.artek.mcp, gateway scope only). There is no separate server or bridge process: your MCP client connects over MCP Streamable HTTP straight to /data/artek-mcp/mcp on the gateway.
  • Tools ready at install. Roughly 90 tools cover gateway health, projects and resources, tags and UDTs, alarms and journals, tag history, gateway configuration, Perspective sessions, security, the audit log, EAM, store-and-forward, the Gateway Network and diagnostics. See Tools.
  • Optional reach you switch on. Three providers ship disabled: database access (Database access), your own project functions as tools (Script endpoints), and calls routed to other gateways on the Gateway Network. Nothing in them is exposed until you enable and scope it.
  • Every call is authenticated and audited. A request needs an API key, or an OAuth bearer token if you turn OAuth on, and every tool call writes an audit line on the gateway.

Read-only by default

A fresh install starts with these settings:

Setting Default
readOnly true: every mutating tool is refused
mutation.allowlist empty, which means deny every target
Request rate 120 requests per minute per key, over a sliding 60-second window
Request body cap 1 MiB
Origin validation on
localhostOnly available, off unless you set it
Destructive-tool name echo (mutation.requireNameEcho) on
Optional providers (scripting, db, federation, vision) disabled

Read-only still reads a lot

Read-only limits what a caller can change, not what it can see. A valid API key can read project source, tag values, alarm and audit records, log text and the security inventory. Treat every key as a gateway credential. Read Security before you connect a client to a production gateway.

Requirements

Requirement Detail
Ignition 8.3.4 or later, gateway scope
MCP protocol revision 2025-06-18; also accepts 2025-03-26 and 2024-11-05
Perspective module optional. When present, the Perspective session tools are registered
Alarm Notification module optional. When present, its tools are registered
Vision module optional. The Vision read tools are registered only when Vision is installed, and are off by default
Network the MCP client must reach the gateway's web port

Where to go next

  1. Install the module and get an API key.
  2. Connect your MCP client.
  3. Read the Security model, then tune Configuration for your gateway.

Licensing and support

The Gateway shows the End User License Agreement at install, and the module does not run until it is accepted. For licensing and support, see artekis.io.

The module contains one Artek-authored component and redistributes no third-party components. Every library it uses at runtime is supplied by the host gateway, so no third-party license text applies to it. OAuth token validation uses only the Java platform's own security and HTTP libraries.

Data handling. The module sends no telemetry to Artek and makes no outbound connection to Artek. Outbound requests go only to endpoints you configure: an OAuth JWKS URL, and Gateway Network peers for federated tool calls.

Specification. Artek-MCP implements the Model Context Protocol, an open specification developed as a project of the Agentic AI Foundation, a directed fund of the Linux Foundation, published under the Apache License, Version 2.0.

Trademarks. Ignition® is a registered trademark of Inductive Automation, LLC. Artek-MCP is an independent Artek product, not affiliated with or endorsed by Inductive Automation. "Model Context Protocol" and "MCP" are marks associated with the Model Context Protocol project, a Series of LF Projects, LLC. Artek-MCP is an independent implementation and is not affiliated with, endorsed by, or certified by the Linux Foundation, the Agentic AI Foundation, LF Projects, LLC, or Anthropic, PBC.