gitcad
Enables agents to create and manipulate 3D CAD models using natural language via MCP, with git-based versioning and manufacturing output generation.
README
gitcad
Agent-first, headless, git-native CAD.
gitcad is a boundary-representation CAD system designed from the ground up to be
driven by agents over MCP, with git as the
source of truth and a browser as the (optional) viewer. It leans on the mature
OpenCASCADE geometry kernel via
cadquery-ocp rather than reinventing
b-rep math — the value lives in the layers around the kernel:
- an intent-based API agents can author without visualizing raw NURBS,
- a verification/render loop so agents model by checking, not hoping,
- associative 2D drawings derived from the 3D model (mechanical drafting),
- a git-native text format so models diff, branch, and merge like code, and
- a privacy-preserving bug loop where failures are auto-reduced to minimal, synthetic, shareable repros.
Website: gitcad.xyz
Why this exists
Agents fall back to shelling out to FreeCAD for anything with complex curves — not because that's good, but because it's what's in the training distribution, and they model blind. gitcad's thesis: wrap the same proven kernel (OCCT) in an intent API plus a deterministic inspect/render loop, make the model text so git works, and make MCP the primary interface so the product is agent-legible from day one.
The six seams
Everything swappable lives behind a small, stable interface (gitcad.seams):
| Seam | Responsibility | Default backend |
|---|---|---|
Kernel |
b-rep geometry ops | OCCT via cadquery-ocp (gitcad.kernel.occt) |
IdentityService |
stable entity IDs (topological naming) | lineage-hash (gitcad.identity) |
DocumentModel |
the feature tree + text (de)serialization | gitcad.document |
Renderer |
headless tessellate → image/glTF | stub |
DrawingEngine |
3D → 2D HLR projection + dimensions | stub |
Storage |
git-backed model + artifact store | stub |
A "major architecture change" should mean replacing one backend, not a rewrite.
Layout
src/gitcad/
seams.py # the six Protocol interfaces — the load-bearing boundaries
errors.py # structured errors that double as bug-repro payloads
identity.py # IdentityService: stable IDs from construction lineage
document.py # DocumentModel: feature tree + canonical text format
kernel/
null.py # pure-Python test backend (no OCCT dependency)
occt.py # OCCT via cadquery-ocp (the real kernel)
report/
fingerprint.py # deterministic failure fingerprints (for dedup)
reduce.py # delta-debug reducer: proprietary model -> minimal synthetic repro
mcp/
server.py # the MCP tool surface (the PRIMARY interface)
docs/adr/ # architecture decision records (the durable intent)
tests/
invariants/ # permanent, architecture-independent properties
golden/ # curated user-visible contracts
regression/ # auto-generated, second-class, expirable
Quick start
pip install --no-deps -e packages/gitcad-core -e packages/gitcad-mech -e packages/gitcad-ecad -e packages/gitcad && pip install pytest
pytest # runs against the pure-Python null kernel
pip install cadquery-ocp # add the real OCCT kernel (~large wheel)
The test suite runs with no geometry kernel installed — the null backend
covers identity, document round-tripping, and reduction. Tests that need real
geometry are marked @pytest.mark.occt and skip when cadquery-ocp is absent.
Status — v0.1
Manufacturing outputs work end to end. From a text model, gitcad produces files you can send to a manufacturer today:
| Domain | Outputs |
|---|---|
| Mechanical | STEP (ISO 10303-21) · STL · dimensioned 2D drawings (SVG + PDF, third-angle front/top/right/iso via OCCT HLR) |
| Electrical | Gerber X2 (copper ×2, mask ×2, silk, profile) · Excellon drill · pick-and-place CSV · manifest |
Working: OCCT kernel (primitives, booleans, fillets, transforms, validation, measurement, entity enumeration) · drawing engine · 2-layer board model with fab-readiness validation · MCP tools for all of it · deterministic, byte-stable outputs (same source → identical Gerbers).
Try it:
pip install cadquery-ocp # after the editable installs above
python examples/bracket.py # → bracket.step, bracket.pdf, bracket.svg, bracket.stl
python examples/blinky.py # → full Gerber/drill/PnP fab package
Next: the cross-domain part standard (interfaces, ports, lockfile versioning),
schematic capture + ERC, DRC engine, associative feature-level dimensions, the
component registry. See docs/adr/ for the reasoning, docs/research/ for the
competitive feature map, and CLAUDE.md for the rules agents must follow.
License
Apache-2.0. The OCCT kernel it binds is LGPL-2.1-with-exception; see NOTICE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。