CAD/CAE Copilot — an AI-native CAD/CAE/CAX workbench for AI agents. Text-to-CAD, text-to-CAE, real build123d/OpenCASCADE geometry, editable parameters, stable topology pointers, deterministic critique, and MCP server tools.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"cad-cae-copilot": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An AI-native CAD/CAE/CAX workbench. An MCP-capable agent writes real build123d / OpenCASCADE geometry, exports STEP/STL/GLB, names the parts, exposes stable topology pointers, runs a deterministic critique, and can continue into CAE — all preserved in one reproducible .aieng package.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Just a Better Chatbot. Powered by Agent & MCP & Workflows.
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Security Weekly
Get CVE alerts and security updates for Cad Cae Copilot and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An AI-native CAD/CAE/CAX workbench. An MCP-capable agent writes real
build123d / OpenCASCADE geometry, exports STEP/STL/GLB, names the parts,
exposes stable topology pointers, runs a deterministic critique, and can
continue into CAE — all preserved in one reproducible .aieng package.
You bring your own MCP client (e.g. Claude Code, Codex, Copilot, Cursor), which carries its own model access. The aieng backend itself needs no API key.
Quick Start · CAD Examples · Why aieng · MCP Setup · Agent Guide
English | 中文
Real STEP/STL/GLB · Editable parameters · Named parts · Stable topology pointers · Deterministic critique · CAD → CAE artifacts · Approval-gated actions
Three ways in — pick one and you're modeling in minutes.
Before you start: you need your own MCP client (Claude Code, OpenAI Codex, GitHub Copilot, Cursor, …) with its own model access. The aieng backend itself needs no API key — your agent connects to it over MCP and drives the workbench through its own harness.
For a first try, Docker (Option 2) is the most reliable — it pins the build123d / OpenCASCADE / CalculiX stack so nothing has to compile on your machine. The local dev install is best once you intend to hack on the code.
Click "Open in GitHub Codespaces" above. The environment sets itself up;
when it finishes loading, run make dev (or python3 scripts/dev.py if make
is unavailable). Then connect an agent and paste the
motor mounting fixture prompt, or the
shorter bracket prompt:
Create a 120 × 80 × 12 mm machined bearing support bracket with a centered
Ø42 mm horizontal bearing bore, four Ø10 mm base mounting holes, and two
mirrored gussets. Preserve the exact dimensions, expose editable parameters,
verify the final geometry, and run the deterministic engineering critique.
Inspect the generated model, named parts, verification results, and stable
@face:* references in the workbench.
Packages the backend, built viewer, MCP HTTP server, build123d / OpenCASCADE dependencies, and CalculiX into one container.
Quick start with Docker Compose (recommended):
docker compose up -d
Or build and run manually:
docker build -t aieng/workbench:local .
docker run --rm -it -p 8000:8000 -p 8765:8765 -v aieng-data:/data aieng/workbench:local
Open the viewer at http://localhost:8000/app/ and point an MCP-over-HTTP client
at http://localhost:8765/sse. Projects and .aieng packages persist in the
aieng-data volume. The container enables AIENG_MCP_MANAGED_APPROVAL=1 by
default, so approval-gated CAD/CAE tools surface through the workbench UI.
Best when