freecad-tool-server

freecad-tool-server

Enables AI agents to programmatically build, analyze, and export 3D CAD geometry using FreeCAD through REST or MCP tools.

Category
Visit Server

README

FreeCAD Tool Server

An HTTP + MCP tool server that lets an AI agent of your choice drive FreeCAD programmatically — building, analyzing, and exporting real 3D CAD geometry through typed tool calls.

Agents call REST endpoints (or MCP tools) to create primitives, run boolean operations, loft airfoils, drill holes, fillet edges, check clearances, run finite-element analysis via Elmer, and export validated STEP files — receiving structured feedback at every step.

Your agent (Claude Code, Claude Desktop, any MCP/HTTP client)
      │  MCP tools  or  JSON over HTTP
      ▼
FreeCAD Tool Server  (main.py, typed models in models.py)
      │  in-process import
      ▼
FreeCAD 1.1 bundled Python  ──►  OpenCASCADE geometry kernel

The server runs inside FreeCAD's bundled Python interpreter — FreeCAD is imported as a module, not shelled out as a subprocess. That's why you launch it with FreeCAD's python.exe, not your system Python.


Prerequisites

  • FreeCAD 1.1+ installed (ships its own Python 3.11).
  • (Optional, for FEM) Elmer and Gmsh on your PATH for the /fem/* endpoints and elmer_*.py runners.

No system Python is required to run the server — FreeCAD's interpreter provides everything.


Setup

1. Install the Python dependencies into FreeCAD's interpreter

Windows

"C:\Program Files\FreeCAD 1.1\bin\python.exe" -m pip install -r requirements.txt

Linux / macOS (adjust to your FreeCAD install)

/path/to/FreeCAD/bin/python -m pip install -r requirements.txt

2. Start the server

Windows — edit the FreeCAD path in start.bat if needed, then:

start.bat

Linux / macOS — set FREECAD_PYTHON to your FreeCAD interpreter, then:

FREECAD_PYTHON=/path/to/FreeCAD/bin/python ./start.sh

The server listens on http://localhost:8000. Interactive API docs (Swagger UI) are at http://localhost:8000/docs.

3. Health check

curl http://localhost:8000/health
# {"status":"ok","freecad_available":true,"freecad_version":"1.1.1",...}

Connect your agent

Option A — MCP (Claude Code, Claude Desktop, any MCP client)

mcp_server.py exposes the tool server over the Model Context Protocol. Point your MCP client at it. For Claude Code, add it to your MCP config:

claude mcp add freecad -- "C:\Program Files\FreeCAD 1.1\bin\python.exe" /path/to/mcp_server.py

or add an entry to your client's MCP settings JSON:

{
  "mcpServers": {
    "freecad": {
      "command": "C:\\Program Files\\FreeCAD 1.1\\bin\\python.exe",
      "args": ["/absolute/path/to/mcp_server.py"]
    }
  }
}

The agent then gets every FreeCAD tool as a native MCP tool.

Option B — Claude Code reading AGENTS.md / CLAUDE.md directly

Clone this repo and open it in Claude Code (or any agent that reads AGENTS.md). The bundled AGENTS.md is a complete operating manual — the modeling loop, every endpoint, the common pitfalls, and the required integration checks. Start the server, tell your agent what to build, and it drives the HTTP API using that guide. A copy is provided as CLAUDE.md so Claude Code loads it automatically.

Option C — Raw HTTP from any language

Every tool is a plain REST endpoint. Minimal stdlib Python client (no extra deps) in tools/freecad_client.py:

from tools.freecad_client import FreeCADClient

fc = FreeCADClient()   # defaults to http://127.0.0.1:8000
fc.tool("POST", "/document/create", name="demo")
fc.tool("POST", "/shapes/add_box", name="b", length=50, width=30, height=10)
info = fc.tool("POST", "/model/get_shape_info", shape_name="b")
print(info["volume_mm3"])   # 15000.0

The core modeling loop

create_document
  → add primitives (add_box / add_cylinder / add_cone / add_wing)
  → boolean ops (boolean_union / boolean_cut / make_hole)
  → inspect (get_shape_info / bounding_box / check_interference)
  → finish (fillet_edges / chamfer_edges)
  → export (export_step)
  → validate (validate_step)   ← aim for is_clean == true, solid_count == 1

See AGENTS.md for the full endpoint reference, edge-selector rules, the in-place boolean-update pattern, and the mechanical integration checks (interference / clearance) that catch spatial errors before export.


Finite-element analysis (optional)

With Elmer and Gmsh installed, the /fem/* endpoints and the elmer_*.py runners cover a broad tutorial set — elasticity, heat, electrostatics, magnetostatics, fluid flow, eigenmodes, and more. These are heavier and require the external Elmer/Gmsh toolchain; the CAD tools work without them.


Repository layout

Path What it is
main.py FastAPI tool server — all HTTP endpoints
session.py FreeCAD session logic (geometry, booleans, export, FEM)
models.py Typed Pydantic request/response models
mcp_server.py MCP bridge — exposes the tools to MCP clients
freecad_bridge.py Headless FreeCAD discovery/import helper
AGENTS.md / CLAUDE.md Agent operating manual (identical content)
elmer_*.py Standalone Elmer FEM tutorial runners
tools/ Client helper, test suite, integration-check hook, example scripts
start.bat / start.sh Launchers (use FreeCAD's bundled Python)

License

MIT.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured