AI Integration | Claude Skill and MCP Setup
The FrameworX AI Designer experience has two components that work as a pair:
The Claude Skill is a lightweight file (SKILL.md) that loads into Claude at the start of every session. It gives Claude baseline FrameworX knowledge and trained instincts: progressive build discipline, schema-then-write patterns, trust-tool-results rules. Without the skill, Claude works but starts every session without context. With it, Claude behaves like an experienced FrameworX engineer from the first message.
Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Together style none
MCP Tools connect Claude directly to the FrameworX engineering environment. Two MCP servers are available depending on your workflow:
AI Designer connects Claude to the live Designer IDE. Every tool call produces immediate visual changes — tags, displays, alarms, and devices appear in real time while the engineer watches. 16 tools cover the full solution lifecycle from create_solution through start_runtime. This is the co-pilot experience — Claude and the engineer work side by side on the same screen.
SolutionMCP connects Claude Code to FrameworX in a file-based workflow, no running Designer needed. Claude generates JSON configuration files following the ExportFormat 1.2 standard, which the engineer imports into Designer for validation and deployment. Twelve tools cover solution creation, object CRUD, schema queries, and documentation search. Particularly effective for analyzing existing projects (inspect structure, audit configurations, extract patterns), generating solutions from specification documents, and batch-building across multiple solutions — all from the command line.
Together, the skill conditions Claude's behavior before the first tool fires, and MCP gives Claude the tools to act on that knowledge. The result is an AI co-pilot that truly understands the platform, and builds solutions correctly from the first response.
Note: AI Runtime is a separate integration that connects AI to running solutions for live data queries and operations interactions. This page covers the Designer integration — the build-time experience. See [AI Runtime Connector](AI Runtime Connector) for runtime setup.
| Component | Purpose | Install Time |
|---|---|---|
| Claude Skill | Prepares Claude for FrameworX sessions | 2 minutes |
| AI Designer | Connects Claude to the live Designer IDE (co-pilot mode) | 3 minutes |
| SolutionMCP | Connects Claude Code to file-based engineering (offline mode) | 3 minutes |
| FrameworX Designer (v10.1.3+) | The IDE that Claude controls (AI Designer) or imports into (SolutionMCP) | Download |
| Info |
|---|
Requires a Claude Pro, Max, Team, or Enterprise plan. Any LLM with MCP protocol support can be used, Claude is our recommendation. |
Which MCP server do I need?
| Scenario | Use |
|---|---|
| Claude Code on the same Windows machine as Designer — want live co-pilot | AI Designer (stdio) |
| Claude Desktop or Claude.ai — want live co-pilot over the network | AI Designer (HTTP/SSE) |
| Claude Code — want to generate configs without a running Designer | SolutionMCP |
You can install both. They register as separate MCP servers and do not conflict.
The Claude Skill is a portable SKILL.md file that follows the Agent Skills open standard. Install it once — it activates automatically whenever you mention FrameworX, SCADA, HMI, or related topics.
frameworx-industrial-platform.skillmkdir -p ~/.claude/skills/FrameworXframeworx-industrial-skillplatform
cp SKILL.md ~/.claude/skills/FrameworXframeworx-industrial-skillplatform/SKILL.md
Claude Code discovers skills automatically — no restart needed.
The same SKILL.md works with any compatible agent:
| Agent | Skill Location |
|---|---|
| GitHub Copilot | .github/skills/FrameworXframeworx-industrial-skillplatform/SKILL.md |
| Cursor | .cursor/skills/FrameworXframeworx-industrial-skillplatform/SKILL.md |
| OpenAI Codex CLI | .codex/skills/FrameworXframeworx-industrial-skillplatform/SKILL.md |
Three connection modes depending on your setup. Pick the one that matches.
Use this when Claude Code and FrameworX Designer run on the same Windows machine. This is the simplest setup — Claude Code launches DesignerMCP directly as a subprocess.
Prerequisites:
Configuration:
Add to your Claude Code MCP settings:
{
"mcpServers": {
"FrameworX-Designer": {
"command": "<ProductPath>\\DesignerMCP.exe",
"transport": "stdio"
}
}
}
Replace <ProductPath> with your FrameworX installation directory. Example:
C:\\Program Files (x86)\\Tatsoft\\FrameworX\\fx-10\\MCP\\DesignerMCP.exe
Use double backslashes in the path.
Use this when Claude runs on a different machine than Designer, or when using Claude Desktop App or Claude.ai (the web chat interface). This mode uses HTTP with Server-Sent Events (SSE), which works across machines, across operating systems, and even across VMs.
How it works: DesignerMCPHttp runs as a lightweight HTTP server on the Windows machine alongside Designer. Claude connects to it over the network using mcp-remote, an open-source MCP-to-HTTP bridge.
Prerequisites:
mcp-remote bridge)Step 1 — Start DesignerMCPHttp on the Windows machine
Open a command prompt and navigate to the MCP directory:
cd "<ProductPath>\DesignerMCPHttp"
dotnet DesignerMCPHttp.dll
This starts the HTTP/SSE server on port 4000. Leave this running — it must be started before Claude.
Important: The MCP server must be running before you launch Claude Desktop. If you restart the server, restart Claude Desktop as well.
Step 2 — Configure Claude
For Claude Desktop App, edit claude_desktop_config.json:
%APPDATA%\Claude\claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"DesignerMCPHttp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"http://127.0.0.1:4000/sse"
]
}
}
}
For Claude.ai (web interface with Claude in Chrome), the same HTTP endpoint works — configure http://127.0.0.1:4000/sse as the MCP server URL.
Step 3 — Restart Claude Desktop
Close Claude Desktop completely (use Task Manager to ensure it is fully closed) and relaunch.
If Designer runs on a different machine than Claude (including a Windows VM accessed from a Mac host):
127.0.0.1 with the IP address of the Windows machine running Designer127.0.0.1 works from the Mac sideExample for a Designer running on 192.168.1.50:
{
"mcpServers": {
"DesignerMCPHttp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"http://192.168.1.50:4000/sse"
]
}
}
}
Use this when you want Claude Code to generate FrameworX configurations offline — no running Designer required. Claude creates JSON files in an Exchange folder, and the engineer imports them into Designer later for validation and deployment.
This is ideal for:
Prerequisites:
Configuration:
Add to your Claude Code MCP settings (.mcp.json in your project root, or global Claude Code config):
{
"mcpServers": {
"FrameworX-SolutionMCP": {
"command": "<ProductPath>\\SolutionMCP.exe",
"transport": "stdio"
}
}
}
Replace <ProductPath> with the MCP directory inside your FrameworX installation. Example:
C:\\Program Files (x86)\\Tatsoft\\FrameworX\\fx-10\\MCP\\SolutionMCP.exe
How the file-based workflow works:
create_solution or open_solution — this creates or opens a <name>-json/ folder under Documents/FrameworX/Exchange/get_table_schema to fetch column definitions, then write_objects to generate JSON filesAvailable tools (12):
| Category | Tools |
|---|---|
| Solution management | list_solutions, open_solution, create_solution |
| Object operations | write_objects, get_objects, delete_objects, rename_object |
| Schema queries | get_table_schema, list_elements, list_dynamics, list_protocols |
| Documentation | search_docs, inspect_external_solution |
Tip: You can install both AI Designer and SolutionMCP side by side. They register as separate MCP servers (
FrameworX-DesignerandFrameworX-SolutionMCP) and do not conflict. Use AI Designer when you want live co-pilot mode, and SolutionMCP when you want offline file generation.
Security Authorization
After restarting Claude Desktop with MCP installed:
- Go to Settings → Connectors
- Find FrameworX-Designer (or DesignerMCPHttp) in the list
- Click Configure and set Tool Permissions to Always Allow
Without this, Claude will prompt for authorization on every tool call. Longer responses that use many tools may fail if permissions are not set to Always Allow.
Claude Code handles tool authorization differently — it prompts inline on first use and remembers the decision for the session. No pre-configuration needed.
Start a new Claude conversation and try:
Without MCP (skill only): Ask "How do I set up FrameworX MCP tools?" — Claude should provide step-by-step instructions from the skill, not a web search.
With AI Designer connected: Ask "Create a new FrameworX solution with a bottling line" — Claude should immediately load the New Solution skill and start building, not spend a response outlining a plan.
With SolutionMCP connected: Ask "Create a new FrameworX solution with 10 motor tags and Modbus communication" — Claude should call create_solution, fetch schemas, and start writing JSON files into the Exchange folder.
If Claude is web-searching for basic FrameworX setup information, the skill may not be enabled. Check Settings → Capabilities → Skills.
If Claude says MCP tools are not connected, verify the server is running and check your config file for typos.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Claude web-searches for FrameworX basics | Skill not loaded | Check Settings → Capabilities → Skills |
| "MCP tools not connected" | Server not running or config error | Verify DesignerMCP/SolutionMCP is running, check config JSON |
| Tools timeout or fail | Permissions not set | Set tool permissions to Always Allow (Claude Desktop) |
| HTTP connection refused | Firewall or wrong IP | Open port 4000, verify IP address |
| "Cannot connect" on Mac → Windows VM | Port forwarding not configured | Configure VM port forwarding for port 4000 |
| Node.js errors with mcp-remote | Node.js not installed | Install from nodejs.org |
| "No active solution" in SolutionMCP | Solution not opened | Call open_solution or create_solution first |
| "Control schemas not found" in SolutionMCP | Missing data file | Ensure ControlSchemas.json is in the MCP folder alongside SolutionMCP.exe |
| SolutionMCP fails to launch | .NET 8 runtime missing | Run dotnet --list-runtimes — install from dotnet.microsoft.com |
Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
Claude Code MCP (project-level): .mcp.json in your project root
Claude Code skills: ~/.claude/skills/FrameworXframeworx-industrial-skillplatform/SKILL.md
SolutionMCP workspace: Documents/FrameworX/Exchange/<SolutionName>-json/
Questions or feedback: