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 starts every session without context. With it, Claude behaves like an experienced FrameworX engineer from the first message.
MCP Tools connect Claude directly to the FrameworX Designer IDE. Every tool call produces immediate visual changes — tags, displays, alarms, and devices appear in real time while the engineer watches. 18 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.
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 for runtime setup.
Looking for Claude Code? If you use Claude Code from the command line, see Claude Code MCP Setup for advanced integration options including file-based engineering without a running Designer.
Component | Purpose | Install Time |
|---|---|---|
Claude Skill | Prepares Claude for FrameworX sessions | 2 minutes |
MCP Bundle (.mcpb) | Connects Claude Desktop to the live Designer IDE | 1 minute |
FrameworX Designer (v10.1.3+) | The IDE that Claude controls |
Requires a Claude Pro, Max, Team, or Enterprise plan.
Any LLM with MCP protocol support can be used; Claude is our recommendation.
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.
Then, on Claude Desktop:
The MCP Bundle is a single .mcpb file that installs the DesignerMCP tools into Claude Desktop with one click — no manual configuration needed.
Prerequisites: FrameworX Designer v10.1.3+ must be installed first. The MCP bundle ships with the product installation.
The mcpb files are located at Documents\FrameworX\AISetup
Repeat this procedure for EACH of the following files:
- frameworx-designer-mcp.mcpb
- frameworx-filesystem.mcpb
1. Open Claude Desktop
2. Go to Menu > File > Settings... > Extensions
3. Click "Advanced Settings"
4. Click "Install Extension"
5. Select the .mcpb file
6. Click "Install"
7. Click "Install" again on the confirmation popup
Note: Anthropic is regularly updating the settings UI, if those steps are not found, check Claude's official documentation for the current location
Without this step, Claude will ask you to approve every single tool call, which breaks longer building sessions.
Test it: Open a new conversation and ask "Create a new FrameworX solution with a bottling line" — Claude should immediately start building, calling create_solution and writing objects.
You're done! Jump to Next Steps.
Use this when Claude Desktop and FrameworX Designer run on different machines — for example, Claude Desktop running on a Mac with FrameworX Designer inside a Windows virtual machine (Parallels, VMware), or FrameworX running on a separate Windows computer on the network.
In this setup, DesignerMCPHttp runs as a lightweight HTTP server on the Windows machine. Claude Desktop connects to it over the network using mcp-remote, an open-source MCP-to-HTTP bridge. All communication happens exclusively through the MCP tools — no shared folders or filesystem server is needed.
Prerequisites:
mcp-remote bridge)On the Windows machine where FrameworX is installed:
Documents\FrameworX\UtilitiesYou should see a console window confirming the server is listening on port 10150. Leave this window open — the server must stay running.
Important: The MCP server must be started before Claude Desktop. If you ever restart the server, you must also restart Claude Desktop.
On the machine where Claude Desktop runs (e.g., your Mac):
node --version
You should see a version number like v22.x.x.
Find and open the configuration file:
Win + R, type %APPDATA%\Claude and press Enter. Open claude_desktop_config.json.Cmd + Shift + G, type ~/Library/Application Support/Claude and press Enter. Open claude_desktop_config.json.If the file doesn't exist, create a new text file with that exact name.
Replace the entire contents with:
If FrameworX is in a VM on the same host machine (e.g., Parallels/VMware on Mac — use 127.0.0.1):
{
"mcpServers": {
"FrameworX-Designer": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"http://127.0.0.1:10150/sse"
]
}
}
}
For Mac + Parallels/VMware: You may need to configure port forwarding in your VM settings to route port 10150 from the Mac host to the Windows guest.
If FrameworX is on a different computer on the network, replace 127.0.0.1 with the IP address of that machine. For example, if the Windows machine is at 192.168.1.50:
{
"mcpServers": {
"FrameworX-Designer": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"http://192.168.1.50:10150/sse"
]
}
}
}
Make sure port 10150 is open in Windows Firewall on the FrameworX machine.
Save and close the file.
Ctrl + Shift + Esc).Cmd + Q.Test it: Ask "Create a new FrameworX solution with a bottling line" — Claude should immediately start building.
If the MCP Bundle does not work for your environment, or you prefer manual control, you can configure Claude Desktop by editing the JSON configuration file directly.
Prerequisites:
Win + R, type %APPDATA%\Claude and press Enterclaude_desktop_config.json in any text editor (Notepad works fine)Replace the entire contents of the file with:
Error rendering macro 'code': Invalid value specified for parameter 'com.atlassian.confluence.ext.code.render.InvalidValueException'{
"mcpServers": {
"FrameworX-Designer": {
"command": "dotnet",
"args": [
"C:\\Program Files\\Tatsoft\\FrameworX\\fx-10\\net8.0\\DesignerMCP.dll"
],
"transport": "stdio"
},
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"C:\\Users\\Public\\Documents\\FrameworX\\Exchange"
]
}
}
}Save and close the file.
Note: The DesignerMCP path above is the default installation location. If you installed FrameworX to a different drive or folder, adjust accordingly. Use double backslashes in all paths.
Ctrl + Shift + Esc), find any Claude processes, and end them.Test it: Open a new conversation and ask "Create a new FrameworX solution with a bottling line" — Claude should immediately start building, calling create_solution and writing objects.
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 the .mcpb is installed in Settings → Extensions. For manual config, check JSON for typos. |
Tools timeout or fail | Permissions not set | Set tool permissions to Always Allow (Step 3) |
MCP Bundle won't install | Claude Desktop outdated | Update Claude Desktop to the latest version |
DesignerMCP won't start (manual config) | .NET 8 not installed or wrong DLL path | Run |
Filesystem server won't start (manual config) | Node.js not installed | Run |
HTTP connection refused (different computers) | Firewall, wrong IP, or server not running | Open port 10150 in Windows Firewall, verify IP, make sure the BAT file is running |
"Cannot connect" Mac → Windows VM | Port forwarding not configured | Configure VM port forwarding for port 10150 |
File | Location |
|---|---|
Claude Desktop config (Windows) |
|
Claude Desktop config (macOS) |
|