As engineers begin exploring FrameworX AI Designer, several questions come up repeatedly. Below are answers to some of the most common questions about how the AI integration works, security considerations, and how to get started.
What AI model do you recommend?
We recommend Claude Opus by Anthropic it performs best with our platform. But MCP is an open protocol. It works with GPT, Copilot, and any model that supports the standard. You’re not locked into any single vendor.
What about security with AI? Isn’t it risky to let AI touch the application?
That’s the right question to ask and it’s exactly what we designed for. Let me walk you through both sides: runtime and designer
MCP for Runtime: The built-in MCP tools for runtime are read-only. AI can query tag values, browse the namespace, read alarm history, pull historian data but it cannot write to tags. Period. That’s the default, and there’s nothing to configure.
If you want AI to write to tags , for example, to adjust a setpoint or acknowledge an alarm you have to explicitly enable that through Custom MCP tools, which is a built-in FrameworX feature. With Custom MCP tools, you decide exactly which variables the AI can access, what operations are allowed, and what security constraints apply usernames, tokens, role-based access, whatever your security policy requires. Nothing is open unless you open it. FrameworX provides the full security infrastructure how you use it is your decision in your solution.
MCP for Designer: The AI can only modify objects that carry the MCP category label which are objects the AI itself created. If you open the Designer and manually edit an object, that MCP label is removed, and the AI can no longer modify it. At any time, you can also remove the MCP category flag from any object you want to protect from AI changes.
On top of that, Designer automatically backs up everything the AI is changing so you always have a restore point. And the AI can only work within the Development execution profile. If you’re not familiar with FrameworX profiles, the platform allows you to configure multiple execution profiles, each with its own read-only conditions, database connections, and PLC connections. Your production profile, your testing profile, your staging environment, AI never touches those. MCP for Designer is restricted to the Development profile only.
So to summarize: read-only by default for runtime. Write access only through custom tools you explicitly configure with your security rules. Designer changes are limited to AI-created objects, automatically backed up, and restricted to the development environment. You’re in full control at every level.
What does the AI actually know about FrameworX? Is it just a generic model?
It knows FrameworX completely. The MCP integration gives the AI access to 73 configuration schemas covering every object, property, method, and best practice in the platform. It does not search the internet or guess. When it creates a tag, wires a display, or writes a script, it is working from the same knowledge base a Tatsoft engineer would use. That is what makes the output production quality rather than a starting point you have to fix.
How can I try this?
Download FrameworX for free at Request an Evaluation - Tatsoft LLC | FrameworX. The free download includes full AI Designer access, so you can build real solutions from your first session. To go deeper, the documentation covers the full AI integration at AI Integration - FrameworX 10.1 - Tatsoft LLC.