Get Claude working with FrameworX — from first install to productive AI sessions in minutes.

AI Integration | How-to Guide

...

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 — build-don't-plan 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.

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. 12 tools cover solution creation, object CRUD, schema queries, and documentation search. This is the offline engineering experience — Claude builds the configuration, the engineer reviews and imports.

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 builds solutions correctly from the first response.

...

Requires a Claude Pro, Max, Team, or Enterprise plan.

Which MCP server do I need?

You can install both. They register as separate MCP servers and do not conflict.

...

Step 1: Install the Claude Skill

...

...

Step 2: Connect

...

MCP Tools

Two Three connection modes depending on your setup. Pick the one that matches.

Option A: AI Designer — Stdio (Claude Code

...

, same Windows machine)

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.

...

Use double backslashes in the path.

...

Option B: AI Designer — HTTP/SSE (Claude Desktop or Claude.ai

...

, any machine)

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.

...

{
  "mcpServers": {
    "DesignerMCPHttp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://192.168.1.50:4000/sse"
      ]
    }
  }
}

...

Option C: SolutionMCP — File-Based Workflow (Claude Code, no Designer needed)

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:

• Generating solution configurations from specifications or documents
• Working on a machine without FrameworX Designer installed
• Batch-building multiple solutions
• Teams where one person runs Claude Code and another reviews in Designer

Prerequisites:

• FrameworX v10.13+ installed (the SolutionMCP executable and schema DLLs ship with the installer)
• .NET 8.0 Runtime installed
• Claude Code installed

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:

1. Claude calls create_solution or open_solution — this creates or opens a <name>-json/ folder under Documents/FrameworX/Exchange/
2. Claude calls get_table_schema to fetch column definitions, then write_objects to generate JSON files
3. Each JSON file follows the ExportFormat 1.2 envelope structure — ready for Designer import
4. The engineer opens Designer, imports the JSON files, validates, and deploys

Available tools (12):

Tip: You can install both AI Designer and SolutionMCP side by side. They register as separate MCP servers (FrameworX-Designer and FrameworX-SolutionMCP) and do not conflict. Use AI Designer when you want live co-pilot mode, and SolutionMCP when you want offline file generation.

...

Step 3: Set Tool Permissions (Claude Desktop)

Security Authorization

After restarting Claude Desktop with MCP installed:

1. Go to Settings → Connectors
2. Find FrameworX-Designer (or DesignerMCPHttp) in the list
3. 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.

...

Verify It Works

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 MCP 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.

...

...

Quick Reference: Config Files

...

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/FrameworX-skill/SKILL.md

SolutionMCP workspace: Documents/FrameworX/Exchange/<SolutionName>-json/

...

Next Steps

• See it in action: [AI Designer In Action](AI Designer In Action)
• Technical reference: [AI Designer Connector](AI Designer Connector)
• Download Designer: tatsoft.com/fx-101 (free evaluation, unlimited tags, all features)

...