Claude Code MCP Setup

Advanced command-line integration for FrameworX with Claude Code.
AI Integration | Claude Skill and MCP Setup | Claude Code MCP Setup

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

Prerequisites for both: FrameworX v10.1.3+ installed, .NET 8.0 Runtime installed, Claude Code installed.

Install the Claude Skill (Claude Code)

If you haven't already installed the skill, copy the SKILL.md file to Claude Code's skills directory:

mkdir -p ~/.claude/skills/frameworx-industrial-platform
cp SKILL.md ~/.claude/skills/frameworx-industrial-platform/SKILL.md

Claude Code discovers skills automatically — no restart needed.

Other AI Agents

The same SKILL.md works with any compatible agent:

AI Designer Setup (Live IDE Co-Pilot)

This connects Claude Code to the running FrameworX Designer IDE on the same Windows machine. Claude Code launches DesignerMCP directly as a subprocess — the simplest possible setup.

Step 1: Add the MCP Server

Open a terminal and run:

claude mcp add FrameworX-Designer -- dotnet "C:\Program Files (x86)\Tatsoft\FrameworX\fx-10\net8.0\DesignerMCP.dll"

This saves the configuration at project level by default. For other scopes:

• -s project — saves to .mcp.json in the project root (shared via version control)
• -s user — saves to global/user-level config, available in all projects

For a global install:

claude mcp add -s user FrameworX-Designer -- dotnet "C:\Program Files (x86)\Tatsoft\FrameworX\fx-10\net8.0\DesignerMCP.dll"

Step 2: (Optional) Add the Filesystem Server

The filesystem MCP server allows Claude to directly read files produced by get_screenshot and inspect_external_solution. Without it, those tools still work but you must manually provide the files. All other Designer tools work independently.

The filesystem server requires Node.js — install from https://nodejs.org if not already present.

claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem "C:\Users\<username>\Documents\FrameworX\Exchange" "C:\Users\Public\Documents\FrameworX\Transfers"

Replace <username> with your Windows username.

Step 3: Verify

claude mcp list

You should see FrameworX-Designer (and filesystem if added) in the list.

Alternative: Manual Configuration

If you prefer editing config files directly, add to your .mcp.json or Claude Code MCP settings:

{
  "mcpServers": {
    "FrameworX-Designer": {
      "command": "dotnet",
      "args": [
        "C:\\Program Files (x86)\\Tatsoft\\FrameworX\\fx-10\\net8.0\\DesignerMCP.dll"
      ],
      "transport": "stdio"
    },
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "C:\\Users\\<username>\\Documents\\FrameworX\\Exchange",
        "C:\\Users\\Public\\Documents\\FrameworX\\Transfers"
      ]
    }
  }
}

Replace <username> with your Windows username. The path shown is the default FrameworX installation location — adjust if you installed to a different drive or folder.

Note: Claude Code handles tool authorization inline — it prompts on first use and remembers the decision for the session. No pre-configuration of permissions is needed.

AI Console Setup (File-Based Engineering)

AI Console connects Claude Code to FrameworX without a running Designer. Claude generates JSON configuration files that the engineer imports into Designer later for validation and deployment.

Step 1: Add the MCP Server

Local machine (stdio):

claude mcp add FrameworX-Console -- dotnet "C:\Program Files (x86)\Tatsoft\FrameworX\fx-10\net8.0\ConsoleMCP.dll"

For a global install:

claude mcp add -s user FrameworX-Console -- dotnet "C:\Program Files (x86)\Tatsoft\FrameworX\fx-10\net8.0\ConsoleMCP.dll"

Remote machine or VM (HTTP):

When FrameworX is on another machine (e.g., Claude Code running on macOS managing FrameworX in a Windows Parallels VM):

claude mcp add --transport http FrameworX-Console http://localhost:10130/mcp

Replace localhost with the remote machine's IP address if needed.

Step 2: Verify

claude mcp list

You should see FrameworX-Console in the list.

Alternative: Manual Configuration

Local (stdio):

{
  "mcpServers": {
    "FrameworX-Console": {
      "command": "dotnet",
      "args": [
        "C:\\Program Files (x86)\\Tatsoft\\FrameworX\\fx-10\\net8.0\\ConsoleMCP.dll"
      ],
      "transport": "stdio"
    }
  }
}

Remote / VM (HTTP):

{
  "mcpServers": {
    "FrameworX-Console": {
      "type": "http",
      "url": "http://localhost:10130/mcp"
    }
  }
}

How the File-Based Workflow Works

1. Claude calls create_solution or open_solution — 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 AI Console Tools (12)

Test Your Setup

AI Designer test: Open Designer, then ask Claude Code: "Create a new FrameworX solution with a bottling line" — Claude should call create_solution and start building in the live IDE.

AI Console test: Ask Claude Code: "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.

Troubleshooting

Quick Reference: Config Files

Next Steps

• Back to main setup: MCP and Claude Skill Setup
• 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)

Community

Questions or feedback:

• Discord: discord.gg/BYhbTfyRyh
• Forum: forum.tatsoft.com