# MCP Module Early Access

**URL:** <https://forum.inductiveautomation.com/t/mcp-module-early-access/113966>\
**Category:** Ignition Early Access\
**Created:** [February 13, 2026, 8:55pm UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966 "2026-02-13T20:55:00Z")\
**Posts on this page:** 8\
**Page:** 4

<div class="post-metadata">

**Author:** ![Andreas\_Wallevik](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andreas_wallevik/32/64045_2.png) [@Andreas\_Wallevik](https://forum.inductiveautomation.com/u/Andreas_Wallevik)\
**Post date:** [September 21, 2026, 11:50am UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966/63 "2026-09-21T11:50:18Z")

</div>

Hey 😊

I tested the endpoint from inside the Gateway container/network namespace as suggested, using a separate curl container with `--network container:standard-gateway-1` and calling `localhost:8088` directly.

The result is still the exact same `403 Forbidden`, so this appears to rule out the Docker host port mapping or anything sitting in front of the Gateway.

Since theres now also another independent reproduction in this thread (thanks @lai.yujing) on a native Windows 11 Gateway with no Docker or reverse proxy involved, showing the same blanket `403` on `/data/mcp/*` while the same API token works correctly against `/data/api/v1/gateway-info`. --- doesn't it seem less likely that this is environment/proxy related?

Regarding handler registration, I haven't found an explicit "handler registered" log entry. However, before creating my `testing-public` server config, a request to:

`/data/mcp/testing-public`

returned the MCP-specific response:

`{ "message": "MCP server not found: testing-public", "url": "/data/mcp/testing-public", "status": "404" }`

After creating that server config, the same route returns 403 instead. Both testing and testing-public also appear under MCP Server Config in Platform Overview.

That seems to indicate that the **`/data/mcp/*`** handler is registered and processing the route, although I haven't found a specific log entry confirming the handler registration itself.

I also searched the Gateway logs for **`McpGatewayHook`** , **`HandlerFactory`** , **`com.inductiveautomation.mcp`** , and **`NullPointerException`** ; there are no handler/NPE errors, only the normal MCP module startup entry.

If there is a specific logger/category I can enable to see the permission check or route registration in more detail, I’m happy to test that. 🫡

---

<div class="post-metadata">

**Author:** ![jim\_lapratt](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@jim\_lapratt](https://forum.inductiveautomation.com/u/jim_lapratt)\
**Post date:** [September 21, 2026, 12:07pm UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966/64 "2026-09-21T12:07:18Z")

</div>

We have created this MCP module if you want to check it out

> **[Artek-MCP — Free Ignition MCP Server Module](https://artekis.io/community/artek-mcp)**
>
> Free Ignition gateway module that turns your gateway into a Model Context Protocol server. 95 tools on install, read-only by default, signed, AS IS. Ignition 8.3.4+.

---

<div class="post-metadata">

**Author:** ![Andreas\_Wallevik](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andreas_wallevik/32/64045_2.png) [@Andreas\_Wallevik](https://forum.inductiveautomation.com/u/Andreas_Wallevik)\
**Post date:** [September 21, 2026, 12:51pm UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966/65 "2026-09-21T12:51:19Z")

</div>

I also reproduced the same 403 on a completely fresh Ignition 8.3.6 Gateway using the same minimal setup. So I can now reproduce this consistently on 8.3.6, 8.3.8 and 8.3.10-SNAPSHOT.

---

<div class="post-metadata">

**Author:** ![Andreas\_Wallevik](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andreas_wallevik/32/64045_2.png) [@Andreas\_Wallevik](https://forum.inductiveautomation.com/u/Andreas_Wallevik)\
**Post date:** [September 21, 2026, 1:34pm UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966/66 "2026-09-21T13:34:36Z")

</div>

Thanks. This is working well for me 🙂

---

<div class="post-metadata">

**Author:** ![atay](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/atay/32/6232_2.png) [@atay](https://forum.inductiveautomation.com/u/atay)\
**Post date:** [September 25, 2026, 2:17am UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966/67 "2026-09-25T02:17:05Z")

</div>

Is Ignition Catalyst modules replacing this MCP Module?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [September 28, 2026, 3:24pm UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966/68 "2026-09-28T15:24:48Z")

</div>

Yes.  
There will be no further releases of the IA MCP module in 8.3, and the new Catalyst Core/Catalyst Agent modules are the new AI/LLM integration offering in [Ignition 2027](https://pages.inductiveautomation.com/ignition-2027), our upcoming major release slated for February.

MCP _server_ functionality (all this module ever offered) as well as MCP _client_ functionality (the Ignition gateway connecting to external MCP servers) is part of the new Catalyst Agent module.

If you're interested in MCP functionality in 8.3 in particular, I'd highly recommend the Artek module a few posts above. They're good folks 🙂

---

<div class="post-metadata">

**Author:** ![Shay\_Johnson](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@Shay\_Johnson](https://forum.inductiveautomation.com/u/Shay_Johnson)\
**Post date:** [November 4, 2026, 3:33pm UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966/69 "2026-11-04T15:33:51Z")

</div>

Now that Ignition 2027 beta is out, you can see what did with MCP functionality and more by checking out the new Catalyst modules. More info [here](https://forum.inductiveautomation.com/t/introducing-ignition-2027-packed-with-ai-charting-and-historian-upgrades/).

---

<div class="post-metadata">

**Author:** ![Shay\_Johnson](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@Shay\_Johnson](https://forum.inductiveautomation.com/u/Shay_Johnson)\
**Post date:** [November 4, 2026, 3:33pm UTC](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966/70 "2026-11-04T15:33:54Z")

</div>

Closed on November 4, 2026, 3:33pm UTC



[Previous page](https://forum.inductiveautomation.com/t/mcp-module-early-access/113966.md?page=3)
