About Gitcad
Gitcad is an MCP server published by gitcad-xyz in the Browser category: agent-first, headless, git-native CAD.
The repository has 1 stars and 0 forks, with the last commit 2 months ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
From source
git clone https://github.com/gitcad-xyz/gitcadThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
✦
Ask AI about Gitcad
Powered by Claude · Grounded in docs
I know everything about Gitcad. Ask me about installation, configuration, usage, or troubleshooting.
Security checks
6 checks have not been run yet.
Releases
v0.7.6v0.7.6 — the SolidWorks answer (P1–P8) · 23 Jul 2026The full SolidWorks attack list from [solidworks-feature-map.md](https://github.com/gitcad-xyz/gitcad/blob/main/docs/research/solidworks-feature-map.md), shipped: P1 Named parameters + equations** — parts as functions (`"=W/2 + wall"`,…
v0.7.5v0.7.5 — hierarchy authoring + the deferral list is empty · 23 Jul 2026Every remaining explicit deferral in the KiCad feature map is now shipped. Hierarchical sheet authoring `SheetEditor.sheet()` places subsheet instances (+ `hier_label`/`global_label`); hierarchies flatten through the SAME `hier_merge`…
v0.7.4v0.7.4 — blind/buried vias and sheet reuse · 23 Jul 2026Blind/buried vias `Via.layer_from`/`layer_to` span (default = through; all existing board text loads unchanged) Span honored by every consumer: Gerber flash, per-span Excellon drill files (`name-top-in1.drl`), DRC clearance, copper…
v0.7.3v0.7.3 — multi-layer and IPC-2581 · 23 Jul 2026Multi-layer boards (2–16 copper)**: top/in1..inN/bottom naming, per-layer DRC and connectivity (inner copper clears only within its own plane; through-vias touch every layer — blind/buried honestly deferred), inner Gerbers (Copper,L<k>,Inr…
v0.7.2v0.7.2 — merge everywhere, checks in the app · 23 Jul 2026Board fine-grained merge** (ADR-0016 complete): components by ref, holes by name, net classes by class; tracks/vias/zones merge as content-identity element sets — a moved track is remove+add and merges cleanly, so branches routing…