Page History
Get Claude working with FrameworX
...
: from first install to productive AI sessions in minutes.
AI Integration | How-to Guide
...
Note: AI Runtime is a separate integration that connects AI to running solutions for live data queries, dashboards, and troubleshooting. This page covers the Designer integration — the build-time experience. See [AI Runtime Connector](AI Runtime Connector) for runtime setup.
...
What You Need
| 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.13+) | The IDE that Claude controls (AI Designer) or imports into (SolutionMCP) | Download |
Requires a Claude Pro, Max, Team, or Enterprise plan.
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 same SKILL.md works with any compatible agent:
| Agent | Skill Location |
|---|---|
| GitHub Copilot | .github/skills/FrameworX-skill/SKILL.md |
| Cursor | .cursor/skills/FrameworX-skill/SKILL.md |
| OpenAI Codex CLI | .codex/skills/FrameworX-skill/SKILL.md |
...
Step 2: Connect MCP Tools
...
- Claude calls
create_solutionoropen_solution— this creates or opens a<name>-json/folder underDocuments/FrameworX/Exchange/ - Claude calls
get_table_schemato fetch column definitions, thenwrite_objectsto generate JSON files - Each JSON file follows the ExportFormat 1.2 envelope structure — ready for Designer import
- The engineer opens Designer, imports the JSON files, validates, and deploys
Available 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.
...
If Claude says MCP tools are not connected, verify the server is running and check your config file for typos.
...
Troubleshooting
| 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 |
...
Quick Reference: Config Files
...