This page summarizes how AI can assist on creating solutions using the MCP for Designer tools
AI Integration → MCP for Designer In Action | AI MCP for Designer Connector
How It Works
- Connect — Claude Desktop connects to Designer via MCP
- Authorize — First tool call triggers an MCP authorization prompt — approve it once
- Describe — Tell AI what you need in plain English
- Watch — Changes appear directly in Designer in real time
- Refine — Continue the conversation to adjust
Table of Contents maxLevel 2 minLevel 2 indent 10px exclude How style none
Visual Feedback
When AI is connected, Designer shows:
- "AI MCP" badge — Orange label in the toolbar
- Orange border — Glowing border around the working area
You always know when AI is actively controlling the Designer.
Example Prompts
| What You Say | What AI Does |
|---|---|
| "Create 10 temperature tags in the Boiler folder" | Creates Tag.Boiler/Temp1 through Temp10 with proper naming |
| "Connect to a Siemens S7-1500 at 192.168.1.100" |
...
| Searches protocols, creates Channel + Node with correct |
...
| settings | |
| "Build a dashboard showing all pump statuses" | Creates Dashboard display with cells for each pump |
| "Add high/low alarms for TankLevel" | Creates alarm items with proper conditions and groups |
| "Where is Tag.Flow1 used?" |
...
| Opens Find Results panel showing all usage locations | |
| "Show me the Tags tab" | Navigates Designer to the UNS Tags view |
| "Delete the old TestDisplay" | Safely deletes the display after checking for references |
| "Rename Tag.OldName to Tag.NewName" | Renames with safe refactoring — all references update automatically |
| "Log in as admin" | Prompts for password, authenticates via designer_action('logon') |
What AI Can Configure
| Module | Objects |
|---|---|
| UNS | Tags, UserTypes (UDTs), TagProviders, Enumerations |
| Devices | Channels, Nodes, Points (all protocols) |
| Alarms | Groups, Items, Areas |
| Historian | Tags, Tables, Storage Locations |
| Displays | Canvas, Dashboards, Symbols |
| Scripts | Tasks, Classes, Expressions |
| Datasets | DBs, Queries, Tables, Files |
| Reports | Forms, WebData |
| Security | Users, Permissions, Policies |
Not Just a Code Generator
| Traditional Generators | MCP for Designer |
|---|---|
| Generate output, then done | Work side-by-side with AI continuously |
| Output goes to files | Changes appear directly in Designer |
| One-shot generation | Iterative conversation with full context |
| Limited to templates | AI understands your entire solution |
| No security awareness | Respects solution permissions and MCP category labels |
AI Skills — Step-by-Step Guides
AI has access to skills — multi-module implementation playbooks that prevent common mistakes.
When you ask AI to configure something complex (e.g., Modbus TCP communication, historian logging), it automatically searches for relevant skills and follows step-by-step best practices.
Discover available skills:
"What skills are available?"
AI uses: search_docs('', labels='skill') to list all published skills.
Get Started
→ Setup instructions:
...
[AI MCP for Designer Connector] → Overview of all AI features: [AI Integration]