cadkit
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cadkitCreate a parametric box with width=10, height=5, depth=3 using variables."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
cadkit — Onshape MCP

Two Model Context Protocol servers for driving Onshape from an LLM:
cadkit— the focus of this fork. A part-modeling server built around one idea: every part should come out idiomatic, fully-defined, and variable-driven — the way a careful human models, not a pile of absolute coordinates. One sketch carries its entities, geometric constraints, and driving dimensions; it's grounded to the origin and parameterized by variables; downstream features select edges and faces by meaning (concave edge, cylindrical face) rather than by transient ids that break when topology shifts.onshape_mcp— the upstream server this repo forked from (hedless/onshape-mcp), kept intact. Broader and assembly-focused (mates, instances, interference, export). Reach for it when you're assembling parts rather than authoring one.
Why two servers?
onshape_mcpis wide;cadkitis opinionated. cadkit deliberately emits a narrower, stricter shape of geometry so that what you get back is parametric and editable, not just present. See PLAN.md for the thesis and roadmap.
Why cadkit models the way it does
A few hard-won principles are baked into the tools (the full list is in PLAN.md):
Grounded + dimensioned, or it warns.
cad_sketch_closereports whether the sketch is grounded to the origin and dimensioned;require_well_formed=truerefuses to ship an under-defined sketch instead of letting the solver place it unpredictably.Variables drive geometry, but only where they earn it. A dimension, an extrude depth, a hole diameter, a fillet radius — all accept a number or an expression /
#variable. Use a variable when a value travels beyond one sketch or is derived (#leg_len - #thick); use a geometric constraint (equal,symmetric) when the relationship lives between entities; use a literal for a true one-off.Select by meaning, not by id.
cad_find_edges/cad_find_facesreturn deterministic ids chosen by geometry (concave edges for fillets, a cylindrical face by radius), so a feature keeps referring to the right thing after the model changes.
Related MCP server: cad-mcp
The cadkit tools (33)
Group | Tools |
Document / studio |
|
Sketch session |
|
Variables |
|
Features |
|
Pattern / mirror |
|
Inspection / lifecycle / I/O |
|
Semantic selection |
|
A sketch is one session: cad_sketch_begin(plane=… | face=<id>), add entities, add geometric
constraints + driving dimensions, then cad_sketch_close. cad_pattern / cad_mirror take the
featureIds of the features to repeat (e.g. an extrude or hole) plus a direction/axis/plane.
A small example (L-bracket, parametric)
cad_set_variable("leg", "2 in"); cad_set_variable("thick", "0.25 in")
sk = cad_sketch_begin(plane="Front")
# draw the L profile with cad_sketch_polyline / line, then:
cad_sketch_constrain("ground_origin", a="ln1.start") # pin to origin
cad_sketch_dimension(kind="length", target="ln1", value="#leg")
# ... fully define ...
cad_sketch_close(require_well_formed=true) # refuses if under-defined
cad_extrude(sketchFeatureId=sk, depth="#thick", operation="NEW")Install
Both servers live in this one repo and share the same Onshape client.
git clone https://github.com/saltyeg/cadkit-mcp.git
cd cadkit-mcp
python -m venv venv && source venv/bin/activate
pip install -e .Credentials
You need an Onshape API access key + secret key from the Onshape Developer Portal. cadkit resolves them in this order:
ONSHAPE_ACCESS_KEY/ONSHAPE_SECRET_KEYenvironment variables, elsethe
onshapeMCP server entry already in your~/.claude.json(so if you've configured theonshape_mcpserver, cadkit reuses those keys — you never paste them twice).
Register with Claude Code
Add to ~/.claude.json (or ~/.claude/mcp.json). The cadkit entry can omit keys if the
onshape entry already has them:
{
"mcpServers": {
"onshape": {
"command": "/abs/path/to/onshape-mcp/venv/bin/python",
"args": ["-m", "onshape_mcp.server"],
"env": { "ONSHAPE_ACCESS_KEY": "…", "ONSHAPE_SECRET_KEY": "…" }
},
"cadkit": {
"command": "/abs/path/to/onshape-mcp/venv/bin/python",
"args": ["-m", "cadkit_mcp.server"]
}
}
}Use the absolute path to the venv's Python. Restart Claude Code after editing the config or after any change to the server code (a running server holds the old module until restart).
API quota — read this before testing
The Onshape free / standard / education-student tiers allow 2,500 successful API calls
per user per year (limits doc). Only
2xx/3xx responses count — 4xx/5xx are free; 429 is a separate short-term burst limit;
402 means the annual budget is spent. A naive live test suite drains this fast.
cadkit's development practice is built around that constraint:
Offline-first tests.
tests/test_cadkit_builders.pyasserts on the JSON the builders emit — parameter ids, enum strings, constraint structure — with zero API calls. This catches the bug class that actually costs debugging time (a wrong/hiddenparameterId).cadkit_mcp/devkit.py— quota-frugal live helpers:ScratchStudioreuses one part studio across checks;measure_fsreturns bbox / volume / count / sketch bbox / named variables in a single FeatureScript eval (SOLID-body filtered, inch-converted).One on-demand live smoke (~6–8 calls), run by hand before a release — only for truths offline can't prove (a variable actually drives geometry; a concave edge actually fillets).
# offline builder tests — free, run anytime
venv/bin/python -m pytest tests/test_cadkit_builders.py -o addopts="" -qLayout
cadkit_mcp/
├── server.py # the cadkit tools + feature JSON builders
├── sketch.py # SketchSession: entities, constraints, grounding, diagnostics
├── selection.py # semantic edge/face finders (FeatureScript-backed)
├── quota.py # successful-call counter behind cad_api_calls
├── hole_template.json # 160-param native Hole feature template
└── devkit.py # quota-frugal live verification helpers
onshape_mcp/ # inherited upstream server (assemblies, mates, export) — see git history
tests/ # offline builder tests (zero-API)
PLAN.md # cadkit thesis + roadmap (P0–P3)Roadmap
cadkit is ordered so the parametric core is correct before feature breadth — see
PLAN.md. Shipped (P0–P2): the sketch session, idempotent variables, parametric
scalars everywhere, extrude/revolve/fillet/chamfer/shell/hole, sketch-on-face, feature-based
pattern/mirror, semantic edge/face selection, plus inspection/lifecycle/IO — cad_measure,
cad_get_variables, cad_delete_feature, cad_suppress, cad_edit_feature, cad_export.
In progress (P3): richer semantic selection (largest/smallest/extreme/adjacency/on-plane done;
by-tag next) and sketch ergonomics (slots, center-point arcs, fillets, construction geometry
done; in-sketch mirror live-verified; in-sketch pattern emits geometric copies). Deferred: cad_rollback, mass/COM in
cad_measure, and tapped threads on the native Hole feature.
Notes
Not tested on assemblies yet, only individual parts
Credits
Forked from hedless/onshape-mcp; the onshape_mcp
server and its assembly tooling are upstream's work. Built on the
Model Context Protocol and the
Onshape REST API. MIT License.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/saltyeg/cadkit-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server