Now that 8.3.5 has shipped without the MCP module, can anyone from IA give an updated target release? Is 8.3.6 the current plan, or has the timeline shifted further out? Trying to factor this into some architecture planning on our end.
Hi, we are planning to release the module with our 2027 release next February.
I'll add that the early access release here will continue working with 8.3 indefinitely, it just won't get any new features added to it. The version of the module released with 2027 will have a proper web UI for configuration and some first-party tools.
On MCP / AI use --- this can end up with adding folders/files within the ignition installation directory / within the project directory eg .md files etc. are these preserved with a gateway backup/restore or does the gateway backup only keep "real" ignition files?
Random files added to the data directory are "undefined behavior" - from what I remember they'll be preserved right now, unless they match certain ignore patterns (hidden files, certain specific filenames) but I wouldn't recommend planning on that behavior staying the same indefinitely.
If you want to guarantee something is restored, you could pretend you're a module and use one of the namespaced folders-by-module-id in the data directory, e.g.
/data/var/my.made.up.module.id/
On the other side I would like a way to clear out a gateway backup of any extra / junk files.
Ignore this post
I'm an idiot and didn't uncheck the box "Require secure connections for API Keys"and therefore was getting a "Forbidden" error when trying to connect to the MCP server...
I've been playing around with this a bit, pretty cool so far!
For me, I had to uncheck the https requirement for the API key before my client could connect. I haven't tried secure communications yet, but I'm using a test environment.
Also, for anyone using Codex as their client, here's what to add to the config.toml file:
[mcp_servers.ignition]
transport = "http"
url = "``http://localhost:8088/data/mcp/testing``"
[mcp_servers.ignition.headers]
X-Ignition-API-Token = "your-token-here"
This looks primarily designed to interact with a runtime environment, is there any roadmap for an MCP server with the SDK to enable clients to assist in application development?