Validated 3D CAD modeling for AI agents via CAiD + OCCT. 107 tools across 22 modules.
Validated 3D CAD modeling for AI agents via CAiD + OCCT. 107 tools across 22 modules.
Valid MCP server (2 strong, 1 medium validity signals). 2 known CVEs in dependencies (1 critical, 1 high severity) Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
3 files analyzed · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: CAID_OUTPUT_DIR
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-dreliq9-caid-mcp": {
"env": {
"CAID_OUTPUT_DIR": "your-caid-output-dir-here"
},
"args": [
"caid-mcp"
],
"command": "uvx"
}
}
}From the project's GitHub README.
An MCP server that gives AI agents validated 3D CAD modeling via CAiD and OCP (OpenCASCADE). No GUI needed — the modeling engine IS the server.
Every geometry operation is validated through CAiD's ForgeResult system, which tracks volume, surface area, and diagnostics. If a boolean silently fails (common with OCCT), the validation layer catches it and tells you why.
You: "Make a box with rounded edges and a hole through the top, show me a preview"
Claude → create_box → fillet_solid_edges → add_hole → preview_object → export_stl
Result: SVG preview + ~/cadquery-output/my_part.stl
Use discover_tools() to browse, or discover_tools(category="query") for a specific category.
| Category | Count | What it does |
|---|---|---|
| primitives | 7 | Box, cylinder, sphere, cone, torus, extruded polygon, revolved profile |
| modify | 4 | Holes, fillets, chamfers, shell — with index-based edge/face selection |
| transforms | 4 | Translate, rotate, scale, mirror |
| booleans | 4 | Union, cut, intersect, multi-combine |
| query | 6 | List edges/faces, measure objects/distances, find nearest edges/faces |
| view | 2 | Section cuts, exploded assembly views |
| scene | 5 | List, info, delete, duplicate, clear |
| export | 5 | SVG preview, STL, STEP, batch STL |
| heal | 3 | Validity checking, shape repair, face simplification |
| io | 3 | BREP export, STEP/BREP import |
| assembly | 5 | Create, add parts, move, rotate, merge |
| compound | 3 | Belt wires, curve arrays, pulley assemblies |
| advanced | 3 | CAiD scripting, linear patterns, tool discovery |
caid-mcp/
├── server.py # Entry point
├── caid_mcp/
│ ├── __init__.py
│ ├── core.py # Scene state, shared utilities
│ ├── types.py # Pydantic result models (v0.6.0+)
│ └── tools/
│ ├── primitives.py # Shape creation (7 tools)
│ ├── modify.py # Holes, fillets, chamfers, shell (4 tools)
│ ├── transforms.py # Translate, rotate, scale, mirror (4 tools)
│ ├── booleans.py # Union, cut, intersect, combine (4 tools)
│ ├── query.py # Geometry inspection and measurement (6 tools)
│ ├── view.py # Section and exploded views (2 tools)
│ ├── scene.py # Workspace management (5 tools)
│ ├── export.py # STL, STEP, SVG preview (5 tools)
│ ├── heal.py # Validation and repair (3 tools)
│ ├── io.py # BREP/STEP import-export (3 tools)
│ ├── assembly.py # Multi-part assemblies (5 tools)
│ ├── compound.py # Belt/pulley systems (3 tools)
│ └── advanced.py # Scripting, patterns, tool router (3 tools)
├── examples/
│ ├── quickstart.py # Install verification script
│ ├── GALLERY.md # Example gallery with prompts
│ └── images/ # Rendered example images
├── tests/
│ └── test_cadquery_mcp.py
├── pyproject.toml
├── LLM_GUIDE.md # LLM-specific usage guide
├── CHANGELOG.md
└── LICENSE
# 1. Create a virtual environment
python -m venv .venv
source .venv/bin/activate # macOS/Linux
# .venv\Scripts\activate # Windows
# 2. Install CAiD (brings in OCP and all dependencies)
pip install caid
# 3. Clone and install this server
git clone https://github.com/dreliq9/caid-mcp.git
cd caid-mcp
pip install -e ".[dev]"
source .venv/bin/activate
python -c "import caid; import mcp; print('All dependencies OK')"
pytest tests/ -v
claude mcp add-json caid '{"type":"stdio","command":"/FULL/PATH/TO/.venv/bin/python","args":["/FULL/PATH/TO/caid-mcp/server.py"]}' --scope user
Replace /FULL/PATH/TO/ with the actual absolute paths to your venv Python and the server.py file.
Or edit ~/.claude.json directly:
{
"mcpServers": {
"caid": {
"type": "stdio",
"command": "/FULL/PATH/TO/.venv/bin/python",
"args": ["/FULL/PATH/TO/caid-mcp/server.py"]
}
}
}
Add the same config to your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonclaude mcp list # from terminal
/mcp # inside Claude Code
Tools in primitives and query return Pydantic models. Each response carries
both a human-readable text block (via __str__) and a typed structuredContent
JSON payload. Agents can read fields like result.volume_mm3 or
result.bounding_box.xlen directly — no more regex on "OK Created..." strings.
create_box("lid", 50, 30, 5)
text: "OK Created box 'lid' | volume=7500.0mm3 | bbox=50.00x30.00x5.00mm"
structured: {ok: true, name: "lid", kind: "box", volume_mm3: 7500.0, bbox: {...}}
Old clients that only read text still work — this is additive, not a wire change.
The query tools let the LLM inspect what it built before modifying it — solving the "blind fillet" problem where the LLM guesses which edge to target.
list_edges("box") → every edge with index, endpoints, length, type
list_faces("box") → every face with index, area, center, normal
find_edges_near_point(...) → "what edges are near (10, 5, 2.5)?"
measure_distance(a, b) → min distance between two objects
Instead of guessing selector strings like ">Z", the LLM can now:
list_edges to see all edges with their indicesfillet_solid_edges(name, radius, edge_indices="[2, 5, 8]") to target exactly those edgesSame for add_hole(face_index=3) and shell_object(face_index=0).
section_view("part", axis="X", offset=5.0) → cut and preview cross-section
exploded_view("assembly", scale=2.5) → push parts outward for inspection
Every CAiD operation returns a ForgeResult with volume tracking. If a boolean union doesn't increase volume, you get a warning with a hint (shapes may not overlap). Silent OCCT failures are caught automatically.
When built-in tools can't do the job, run_cadquery_script (name kept for API compatibility) gives full access to CAiD and OCP:
script = """
from caid.vector import Vector
from OCP.BRepPrimAPI import BRepPrimAPI_MakeBox
from OCP.gp import gp_Pnt
# Use CAiD helpers or raw OCP calls
result = caid.make_box(20, 20, 10)
"""
Security note:
run_cadquery_scriptexecutes arbitrary Python in a subprocess with no sandboxing. The subprocess has full filesystem and network access. This is safe when the MCP server is used locally with trusted clients (e.g., Claude Code on your own machine). Do not expose this server to untrusted users without adding sandboxing — see Planned Fixes below.
All exports go to ~/cadquery-output/ by default (directory name kept for backward compatibility). Override with:
export CAID_OUTPUT_DIR=/your/path
Or in the MCP config:
{
"env": { "CAID_OUTPUT_DIR": "/your/stl/folder" }
}
Real parts built through CAiD MCP tools. Each example highlights validated geometry, query-before-modify, and section views — things other CAD-for-AI tools can't do. See the full gallery for tool sequences and workflow breakdowns.
Claude Code / Claude Desktop / any MCP client
│
│ stdio (JSON-RPC)
▼
MCP Server (server.py)
│
├── tools/primitives — create shapes
├── tools/modify — holes, fillets, chamfers, shell
├── tools/transforms — move, rotate, scale, mirror
├── tools/booleans — union, cut, intersect
├── tools/query — geometry inspection and measurement
├── tools/view — section cuts, exploded views
├── tools/scene — workspace management
├── tools/export — STL, STEP, SVG preview
├── tools/heal — validation, repair, simplification
├── tools/io — BREP/STEP import-export
├── tools/assembly — multi-part assemblies
├── tools/compound — belt/pulley systems
└── tools/advanced — scripting, patterns, tool router
│
▼
CAiD → OCP (OpenCASCADE) kernel
│
▼
STL / STEP / BREP / SVG files
"CAiD is not installed" — Make sure you installed CAiD in the same venv: pip install caid
"OCP is not installed" — OCP is installed automatically as a dependency of CAiD. If missing: pip install OCP
Claude Code doesn't show tools — claude mcp list to check registration. Make sure the path to your venv's Python binary is absolute. Restart Claude Code.
SVG preview is blank — Object might have zero volume. Use list_objects to check dimensions.
Fillet/chamfer fails — Try heal_object first, then retry with a smaller radius. Use list_edges to verify the shortest edge length.
Tests failing — Make sure you're in the venv: source .venv/bin/activate && pytest tests/ -v
run_cadquery_script — The scripting escape hatch currently runs arbitrary Python with no restrictions. Planned: restricted imports whitelist, filesystem jailing to OUTPUT_DIR, network access disabled. Until then, only use with trusted MCP clients.CAiD MCP was co-developed by Adam Steen and Claude (Anthropic).
MIT — see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.