onshape-jamcp
It is an MCP server for Onshape CAD that lets an AI assistant browse, model, inspect, assemble, visualize, and export parts, using millimeters by default or inches.
Find and inspect Onshape documents, tabs, features, parts, faces/edges, variables, configurations, and assemblies.
Create documents/elements and model parts with sketches, extrude, revolve, patterns, mirror, shell, boolean, fillet, chamfer, parameter updates, and feature deletion.
Add custom features such as Thread Creator, set variables and configuration inputs, rename parts/tabs, and insert/mate assembly instances.
Measure bounding boxes, volume, surface area, mass, faces, and edges; run read-only FeatureScript queries.
Capture screenshots with optional image review, or save images without sending them to the LLM.
Export STEP, STL, Parasolid, or IGES files.
Use raw Onshape REST API calls as an advanced escape hatch.
Check server settings and Onshape credentials; enforce read-only mode when configured.
Click on "Deploy 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., "@onshape-jamcp Model a 60×40 mm plate 8 mm thick with four 5 mm holes and show a screenshot"
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.
onshape-jamcp
Just Another MCP server for Onshape CAD. It lets an AI assistant (Claude, Cursor, VS Code, any MCP client) find your documents, model parts, measure them, look at them and export them - in millimeters by default, with a switch for inches, and a switch that decides whether the assistant gets to see screenshots (which costs tokens) or not.
Status: alpha, verified live. 440+ automated tests run against a simulated Onshape, and the tools were checked against real Onshape accounts (free plan) on geometry with a known answer.
scripts/smoke_test.pypassed 31/31 checks (2026-11-14): sketch → extrude → fillet → hole → edit → screenshot → STEP/STL export, with orientation and dimensions measured. On 2026-11-16 chamfer, assemblies with mates, ThreadCreator threads, part naming, variables, configurations, patterns, mirror, revolve, shell, boolean and OAuth sign-in were checked the same way, and 87 of those checks were re-run on a fresh account. Not yet verified live: paid-plan and enterprise behavior, threads on a configurable bolt under M18, and OAuth over a real one-hour expiry - see what is verified. Re-run the smoke test on your own account (see below).

Highlights
📏 Metric by default | Every length you send or receive is in mm. Set |
👁️ Screenshot review toggle |
|
🔒 Read-only mode |
|
🧰 37 focused tools | Documents, sketch → extrude / revolve → patterns, mirror, shell, boolean, fillet/chamfer, edit parameters, measure, faces/edges, assemblies, screenshots, STEP/STL export - custom Feature Studio features such as Thread Creator, variables, configurations, part naming, plus escape hatches (raw feature JSON, FeatureScript, any REST endpoint). |
🧪 Honest feedback loop | Every modeling tool reports the feature's health ( |
Related MCP server: onshape-mcp
Quick start
1. Create API keys at https://cad.onshape.com/user/developer (tick Read and Write; Delete
only if you want delete_feature). Copy the secret immediately - Onshape shows it once.
2. Add the server to your MCP client.
Claude Desktop, one click: install uv
once, download the installer
onshape-jamcp.mcpb,
open it, paste your two keys into the form and click Install - no config file to edit.
Details and troubleshooting.
Any client, by hand - Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"onshape": {
"command": "uvx",
"args": ["onshape-jamcp"],
"env": {
"ONSHAPE_ACCESS_KEY": "your-access-key",
"ONSHAPE_SECRET_KEY": "your-secret-key",
"ONSHAPE_UNITS": "metric",
"ONSHAPE_SCREENSHOT_REVIEW": "true"
}
}
}
}Claude Code: claude mcp add onshape -e ONSHAPE_ACCESS_KEY=... -e ONSHAPE_SECRET_KEY=... -- uvx onshape-jamcp
To run it from a checkout instead (to work on the code), replace the command with
"command": "uv", "args": ["run", "--directory", "/path/to/onshape-jamcp", "onshape-jamcp"]. More clients and details: docs/getting-started.md.
3. Ask for something:
"Create a document called 'Bracket'. In a new Part Studio model a 60 × 40 mm plate, 8 mm thick, with four 5 mm holes 6 mm from the corners and 4 mm fillets on the vertical edges. Show me a screenshot when you're done."
Examples
Plain-language requests that work today. Every modeling reply says what changed (parts, volume), so the assistant - and you - can see a feature really did something. The numbers are what the tools measured on live Onshape; recipes with the exact calls are in docs/how-to.md.
A plate with holes and rounded corners, then a change of mind
"Create a document 'Bracket' with a 60 × 40 mm plate, 8 mm thick, four 5 mm holes 6 mm from the corners and 4 mm fillets on the vertical edges. Then make the plate 12 mm thick."
The plate is sketched on the Top plane, extruded, filleted and drilled; the later change edits the extrude's depth and everything after it rebuilds. The part's bounding box confirms 12 mm.
A part of revolution
"Model a sleeve, outer diameter 40 mm, inner diameter 20 mm, 30 mm tall, by revolving a profile. Call the part 'Sleeve'."
A rectangle plus a construction line as the axis, revolved 360°: 28 274 mm³ (π × (20² − 10²) × 30),
named Sleeve.
A wheel with a configurable number of spokes
"Make a hub, Ø40 × 10 mm, with spokes 6 mm wide reaching 50 mm from the centre, repeated around the hub. The number of spokes is a variable. Add a configuration with 3 and 6 spokes."
One spoke is patterned around the hub's axis with circular_pattern, the count comes from a variable
that a configuration input drives: 17 979.92 mm³ with 3 spokes and 23 393.46 mm³ with 6.
A parametric bolt and nut, M10 or M18
"Model a hex bolt and nut with a Size configuration (M10 / M18) and a Length input. All sizes from variables. Add the threads."
Head, shank, nut and hole follow the Size variables (an M18 nut is 15.8 mm high, the shank Ø18);
threads use Onshape's Thread Creator feature script, which must be available on your account
(threads).
Repeat, mirror and hollow
"In a 100 × 100 mm, 5 mm plate cut a Ø6 hole 10 mm from the corner and repeat it 3 times, 20 mm apart, in 2 rows 30 mm apart." - "Mirror this part across the Right plane." - "Shell this box to 2 mm walls, open at the top."
A grid of six holes removes exactly 6 × 141.37 mm³; the mirror doubles the volume; a 40 × 30 × 20 mm box (24 000 mm³) shelled to 2 mm walls, open at the top, keeps 7 152 mm³.
Join parts in an assembly
"Put the bolt and the nut into an assembly and fasten them together."
Both are inserted and joined with a mate; the reply lists where each instance ended up, because an accepted mate is not proof that anything moved.
Measure, look, export
"How big is the 'Sleeve' part and what is its volume?" - "Show me a screenshot from the front."
"Export it as STEP."
Bounding box, volume and surface area come from Onshape's own measurement (mass only if you assigned
a material); the screenshot is sent to the assistant (or only saved, see
ONSHAPE_SCREENSHOT_REVIEW); the STEP file lands in the output folder.
Look but do not touch
"List my documents and describe how 'Bracket' was built." (with
ONSHAPE_READ_ONLY=true)
Every tool that can change a document is removed, so the assistant can only read.
Verify it works against your account
cp .env.example .env # fill in the two keys
uv run python scripts/smoke_test.py # on a free plan add --public (see below)It creates a throw-away document (private; on a free plan Onshape only allows public ones, so pass
--public), models a plate, checks the dimensions/orientation/hole volume/fillets/edit/screenshot/
STEP+STL export numerically, then moves the document to Onshape's trash.
It prints PASS/FAIL per check. This is the step that confirms the assumptions a simulated
Onshape cannot (plane orientation, face normals, extrude direction).
Settings
Set as environment variables (the env block of your MCP client) or CLI flags. The important ones:
Variable | Default | Meaning |
| - | Required (or OAuth, next row). API keys. |
| - | Alternative to API keys: your own Onshape OAuth app, then |
|
|
|
|
| Send screenshots to the LLM ( |
|
| Hide all write tools. Flag: |
|
| Enterprise: |
Everything else (image size, output folder, timeout, auth mode, API version, log level) is in docs/configuration.md.
Tools
Group | Tools |
Server |
|
Documents |
|
Inspect |
|
Model |
|
Names, variables, configurations, assemblies |
|
Look & export |
|
Escape hatch |
|
Full parameter reference (generated from the code): docs/tools.md.
Documentation
Getting started - keys, installing in each client, first prompt
Claude Desktop installer - one-click
.mcpb, what the form asks, troubleshootingConfiguration - every setting, units, precedence
OAuth sign-in - sign in with your Onshape account instead of API keys
How-to recipes - holes, fillets, edits, inches, export, read-only, advanced features
Threads and custom features - ThreadCreator: bolt and nut example, every option, how to check it
Parametric modeling - names, variables, configurations (M10 / M18) and assemblies
Screenshots & token cost - what the review toggle does and when to use it
Tool reference - all tools and parameters
Development - architecture, tests, adding a tool
Publishing - PyPI and Glama
Comparison - how this relates to the other Onshape MCP servers
Security notes
API keys stay in your MCP client's config / environment. They are never returned by any tool, never logged, and requests are HMAC-signed so the secret is not even sent over the wire. With OAuth the tokens live in a per-user file and are likewise never returned, logged or sent anywhere but Onshape.
Onshape's free plan makes every document public. Do not model confidential work there.
Write tools act as you on your real documents. Use
ONSHAPE_READ_ONLY=truewhen you only want the assistant to look around, and rely on Onshape's version history as your undo.With screenshot review on, rendered images are sent to your LLM provider like any other message.
Acknowledgements
Prior art that shaped this project: hedless/onshape-mcp (MIT; the Onshape feature JSON conventions were cross-checked against it) and altendky/onshape-mcp. See docs/comparison.md.
License
MIT. Not affiliated with or endorsed by PTC / Onshape.
Available Tools
37 toolsadd_custom_featureAdd custom featureA
Add a custom feature (a Feature Studio script such as Thread Creator) to a Part Studio. Find its feature_type and parameter IDs with list_custom_features first. Returns the new feature_id and its health status; if that is ERROR or WARNING, inspect it with list_features(feature_id=...), then fix it with update_feature or remove it with delete_feature.
Inputs: element_id (required), document_id (required), feature_type (required), name, +4 more. Returns: object
add_featureAdd raw feature (advanced)A
Advanced escape hatch: add any Onshape feature from raw JSON - revolve, patterns,
sweeps, holes, and so on. Copy the structure from an existing feature
(list_features with feature_id) or from onshape_api_request on the Part Studio
featurespecs endpoint. Raw JSON uses Onshape's native units (lengths are written as
expressions like '10 mm').
Inputs: feature (required), element_id (required), document_id (required), workspace_id. Returns: object
add_mateAdd a mateA
Join two part instances of an Assembly with a mate. Pick a spot on each: for a nut on a bolt use the bolt's circular end edge (at 'center') and a face of the nut (at 'centroid'), with mate_type 'cylindrical' (free to turn and slide) or 'fastened'. The first instance stays where it is if it is grounded; the second moves to satisfy the mate. Returns the real status and both instances' resulting positions. Only when the user asks for an assembly. Note: the centroid of a threaded face can sit ~0.2 mm off the thread's axis.
Inputs: first (required), second (required), mate_type (required), assembly_id (required), +5 more. Returns: object
booleanBoolean (union, subtract, intersect)A
Combine whole parts: join them (union), cut one with another (subtract: a bolt hole shaped like a part) or keep what they share (intersect). Part IDs change when parts merge, so call list_parts afterwards. The reply says what changed (parts removed, volume).
Inputs: tools (required), operation (required), element_id (required), document_id (required), +5 more. Returns: object
capture_screenshotCapture screenshotARead-only
Render a shaded screenshot of a Part Studio or Assembly from one or more standard
camera angles. Images are always saved to disk. Whether they are also returned to you for
visual inspection depends on the review flag / server setting - with review off you get
only paths and metadata, which keeps token use low. Use it to visually verify what you
built (shape, hole placement, orientation).
Inputs: element_id (required), document_id (required), views, width, +6 more.
chamferChamfer edgesA
Bevel edges with an equal-distance chamfer: a flat, angled cut that takes the same
distance off both faces at each edge (a 45 degree bevel on a right-angle edge). Use it for
lead-in bevels, bolt and shaft tips and to break sharp edges; use fillet instead for a
rounded blend. The part must already exist (extrude first) and the edge IDs come from
get_body_details. It appends one chamfer feature at the end of the feature tree and
returns its feature_id, name and health (OK / WARNING / ERROR - a distance too large for
the geometry gives ERROR with a warning, but the feature still exists). It does not measure
the result: confirm with get_part_properties (the volume drops) or a screenshot. Change
the size later with update_feature (parameter width), remove it with delete_feature.
Only equal distances are supported; for a two-distance or distance-and-angle chamfer use
add_feature with raw JSON.
Inputs: distance (required), edge_ids (required), element_id (required), document_id (required), +2 more. Returns: object
circular_patternCircular patternA
Repeat parts, features or faces around an axis (a wheel's spokes, bolt holes on a circle). Pattern the FEATURE that makes one spoke or hole (feature_ids) so the copies merge or cut as it does; pattern parts (part_ids) to get separate copies. Put the count in a variable ('#spokes') when it should be configurable. The default name shows the count ('Circular pattern x6'). The reply says what changed (parts, volume).
Inputs: axis (required), count (required), element_id (required), document_id (required), +11 more. Returns: object
create_documentCreate documentA
Create a new, empty-looking Onshape document in the user's account and return its
document_id, workspace_id, name, url and the tabs it already has (Onshape usually adds a
'Part Studio 1' and an 'Assembly 1': reuse and rename them before adding more with
create_element). Private by default. Onshape's FREE plan only allows PUBLIC documents:
the call then fails with nothing created and a message to ask the user, because a public
document is visible to everyone; retry with public=true only after they agree. Use it only
when the user wants a new document; to work in an existing one find it with
list_documents. There is no tool to delete a document, so tell the user a scratch
document stays in their account until they delete it in Onshape.
Inputs: name (required), public, description. Returns: object
create_elementCreate Part Studio or AssemblyA
Add a new tab to a document and return its element_id, name and kind: a Part Studio
(where sketches, extrudes and the other features build parts) or an Assembly (where parts
are inserted and mated). Use it when the document has no suitable tab - a new document
already has a Part Studio and an Assembly, so check get_document first and reuse them
instead of piling up empty tabs. Give it a descriptive name (a tab still called 'Part
Studio 1' is flagged has_default_name). The new tab is empty: model in it with
create_sketch / extrude, or fill an Assembly with insert_instance. It does not
create parts, sketches or documents (create_document makes those).
Inputs: name (required), document_id (required), kind, workspace_id. Returns: object
create_sketchCreate sketchA
Create a sketch of 2D shapes on a plane or planar face. Point coordinates are [x, y]
in the sketch's own axes, in the configured length unit (mm by default). Returns the
sketch's feature_id, to pass to extrude. Tip: verify placement afterwards with
get_part_properties or a screenshot.
Inputs: shapes (required), element_id (required), document_id (required), name, +2 more. Returns: object
delete_featureDelete featureADestructive
Permanently remove one feature from a Part Studio (an extrude, a fillet, a variable, a
pattern, ...). Use it to undo a feature that went wrong (status ERROR, or a warning that
nothing changed) or that is no longer wanted; to change a feature instead, use
update_feature. Features that depend on the deleted one fail afterwards (deleting a
sketch breaks the extrude that uses it), so delete from the end of the tree backwards, or
delete the dependents too, and check list_features for ERROR statuses. The call returns
only the deleted feature_id. There is no trash: only Onshape's version history can bring
the feature back.
Inputs: element_id (required), feature_id (required), document_id (required), workspace_id. Returns: object
export_modelExport model to fileARead-only
Export a Part Studio or Assembly to a CAD/mesh file (STEP, STL, Parasolid, IGES) on the machine running this server and return the file path. Does not modify the document. STL sizes follow the configured unit system.
Inputs: element_id (required), document_id (required), format, filename, +2 more. Returns: object
extrudeExtrude sketchA
Extrude all closed regions of a sketch into a solid, or cut with it (operation 'remove'). The default direction follows the sketch plane's normal. For a sketch on a part's own face that normal points OUT of the part, so to cut a hole or pocket INTO the part pass opposite_direction=true (verified on live Onshape; without it nothing is cut). Always confirm with get_part_properties - the volume must drop. For operation 'new' the reply lists the created parts (parts_created) and names them when part_name is given.
Inputs: depth (required), element_id (required), document_id (required), sketch_feature_id (required), +8 more. Returns: object
filletFillet edgesA
Round edges with a constant-radius fillet: a smooth, curved blend between the two faces
that meet at each edge. Use it to soften corners and sharp edges; use chamfer instead for
a flat, angled bevel. The part must already exist (extrude first) and the edge IDs come
from get_body_details. It appends one fillet feature at the end of the feature tree and
returns its feature_id, name and health (OK / WARNING / ERROR - a radius too large for the
geometry gives ERROR with a warning, but the feature still exists). It does not measure the
result: confirm with get_part_properties (the volume changes slightly) or a screenshot.
Change the radius later with update_feature (parameter radius), remove it with
delete_feature.
Inputs: radius (required), edge_ids (required), element_id (required), document_id (required), +2 more. Returns: object
get_assemblyGet assemblyARead-only
Read an Assembly tab: what it contains, where everything sits and what is mated. Call it
before changing an assembly (to get the instance IDs add_mate needs after
insert_instance) and after add_mate to confirm a part really moved - an accepted mate
is not proof. Read-only, one request, nothing is changed. It returns instances
(instance_id, name and suppressed; for an inserted single part also type 'Part' and the
part_id and element_id of its source - an instance of a whole Part Studio carries only its
id and name, so those fields are then absent), placements (the instance path, fixed,
and position: the translation of its origin in the configured length unit - rotation is
not reported) and mates (feature_id, name, type, suppressed). An empty assembly gives
empty lists. For the parts of a Part Studio use list_parts; for the tabs of a document
use get_document; for volume or size use get_part_properties on the Part Studio.
Inputs: element_id (required), document_id (required), workspace_id. Returns: object
get_body_detailsGet faces and edgesARead-only
List the faces (and optionally edges) of each part with their IDs, geometry type,
area, a point on the face and its outward normal, all in the configured length unit. Use
face IDs as plane in create_sketch to sketch on a face, and edge IDs for fillet /
chamfer. Output is capped for very large parts.
Inputs: element_id (required), document_id (required), part_id, workspace_id, +2 more. Returns: object
get_configurationGet configuration inputsARead-only
List the configuration inputs of a Part Studio (for example a 'Size' list with M10 and
M18, or a 'Length'), with their options and defaults. Names are the labels shown in
Onshape; for an input made in Onshape's UI the generated id (and option_ids) are shown
beside them. Other tools take a configuration such as {"Size": "M18"} (labels or IDs)
to measure or look at one variant.
Inputs: element_id (required), document_id (required), workspace_id. Returns: object
get_documentGet documentARead-only
Describe one document: its main workspace ID and every element (tab) in it - Part
Studios, Assemblies, Drawings, imported files - with their element IDs and types. A tab
flagged has_default_name still carries Onshape's placeholder name: rename it with rename
to say what it holds.
Inputs: document_id (required), workspace_id. Returns: object
get_part_propertiesMeasure part or Part StudioARead-only
Measure geometry: the axis-aligned bounding box (min/max/size) plus volume, surface area, mass and centroid per part, in the configured length unit. Use it to verify dimensions and orientation after modeling. Mass is only meaningful if the part has a material assigned in Onshape.
Inputs: element_id (required), document_id (required), tight, part_id, +2 more. Returns: object
get_settingsGet server settingsARead-only
Show this server's active settings: the unit system every length uses (metric = mm by default, or imperial = inches), whether screenshots are sent to you for visual review, read-only mode, and the Onshape API target. Never reveals API keys. Call this first so you know which unit to use for lengths.
Inputs: no named parameters. Returns: object
insert_instanceInsert a part into an assemblyA
Insert a part (or a whole Part Studio) into an Assembly and return the new instances' IDs and names. Name the Assembly tab (rename) if it still says 'Assembly N'. Only when the user asks for an assembly. Join parts with add_mate.
Inputs: assembly_id (required), document_id (required), source_element_id (required), fixed, +4 more. Returns: object
linear_patternLinear patternA
Repeat parts, features or faces in a straight line (a row of holes, ribs, legs); add
a second direction for a grid. distance is the spacing between neighbouring instances.
Pattern the FEATURE that makes one hole or rib (feature_ids) so the copies cut or merge as
it does. The default name shows count and spacing ('Linear pattern x4 @ 20 mm'). The
reply says what changed (parts, volume).
Inputs: count (required), distance (required), direction (required), element_id (required), +14 more. Returns: object
list_custom_featuresList custom featuresARead-only
List custom features (Feature Studio scripts such as Thread Creator) that add_custom_feature can add: feature_type, namespace and every parameter with its type, unit, default and options. Also lists the custom features this Part Studio already uses. Built-in Onshape features are not listed - use the dedicated tools for those.
Inputs: element_id (required), document_id (required), workspace_id, feature_studio_url. Returns: object
list_documentsList documentsARead-only
Find Onshape documents: returns each one's document_id (every other tool needs it),
name, modified_at and owner, newest first unless sort_by says otherwise. Start here when
the user names a document: search with query, narrow with scope (your own, created by
you, shared with you, recent, or public). To open one document and see its tabs use
get_document; to make a new one create_document. Read-only. A full page includes a
next_offset: pass it as offset for the next page.
Inputs: limit, query, scope, offset, +1 more. Returns: object
list_featuresList featuresARead-only
List the feature tree of a Part Studio in order: features with feature_id, name,
feature_type (newSketch, extrude, fillet, ...), suppressed and health status (OK / WARNING
/ ERROR), plus the rollback_index. Use it to find the feature_id that update_feature or
delete_feature needs, to see why a part looks wrong (an ERROR feature built no
geometry), or - with feature_id - to read one feature's full raw JSON as a template for
add_feature or to learn its parameter IDs. The modeling tools already return the health
of the feature they add, so do not call this after every step: Onshape limits this
endpoint per day (a free plan can hit a 429 with a many-hour wait after heavy polling).
Read-only. For the parts it produces use list_parts; for variables list_variables.
Inputs: element_id (required), document_id (required), feature_id, workspace_id. Returns: object
list_partsList partsARead-only
List the parts (solid and surface bodies) a Part Studio currently produces: part_id,
name, body_type and hidden, one request, read-only. Use it to get the part IDs that other
tools take - get_part_properties and get_body_details (to look at one part), rename,
only_parts / merge_with / part_ids of extrude and the pattern tools, boolean,
insert_instance. Call it again after anything that merges or splits parts (a boolean, an
extrude that adds): IDs can change. A part flagged has_default_name is still called
"Part N": give it a descriptive name with rename. For the feature tree use
list_features; for the tabs of a document get_document.
Inputs: element_id (required), document_id (required), workspace_id. Returns: object
list_variablesList variablesARead-only
List the variables of a Part Studio: name, type, the expression it was set with and its current value (lengths in the configured unit, angles in degrees). A variable that depends on a configuration input also shows configured_by and its value per option. Reference a variable as '#name' in sketch sizes, extrude depths, fillet radii, thread pitch, etc.
Inputs: element_id (required), document_id (required), workspace_id. Returns: object
mirrorMirrorA
Mirror parts, features or faces across a plane. Mirroring a part gives a second part (operation 'new') or merges the copy into the original ('add'); mirroring the feature that makes one half builds a symmetric part. The default name shows the plane ('Mirror (Right)'). The reply says what changed (parts, volume).
Inputs: plane (required), element_id (required), document_id (required), name, +7 more. Returns: object
onshape_api_requestCall any Onshape API endpointADestructive
Escape hatch: call any Onshape REST endpoint directly. Use it for things the dedicated tools do not cover. WARNING: this is the raw API - lengths are in METERS (no unit conversion), POST/DELETE can change or destroy data, and in read-only mode only GET is allowed. Large responses are truncated.
Inputs: path (required), method (required), body, query. Returns: object
renameRename a part or tabAIdempotent
Give a part, or a whole tab (Part Studio / Assembly), a descriptive name. Do this by default: a part still called 'Part 2' or a tab still called 'Part Studio 1' says nothing. Keep a name the user chose; rename only placeholders (flagged has_default_name by get_document and list_parts) unless the user asks otherwise.
Inputs: name (required), element_id (required), document_id (required), part_id, +1 more. Returns: object
revolveRevolve sketchA
Revolve the closed regions of a sketch around an axis into a solid of revolution (a bottle, a pulley, a washer) or cut a groove with it (operation 'remove'). Draw the profile on one side of the axis and, in the same sketch, the axis as a construction line. The reply says what changed (parts, volume) and lists the created parts.
Inputs: element_id (required), document_id (required), sketch_feature_id (required), axis, +9 more. Returns: object
run_featurescriptEvaluate FeatureScriptARead-only
Evaluate a read-only FeatureScript snippet against a Part Studio and return its result. Powerful for queries the other tools do not cover (face counts, distances, evaluating selections). It cannot modify the document. NOTE: lengths inside FeatureScript results are in METERS, not the configured unit.
Inputs: script (required), element_id (required), document_id (required), workspace_id. Returns: object
set_configuration_inputAdd or change a configuration inputAIdempotent
Add a configuration input to a Part Studio, or replace the input of the same name. Only
when the user asks for configurations. To make dimensions depend on a list input, use
set_variable with by_option.
Inputs: name (required), element_id (required), document_id (required), kind, +5 more. Returns: object
set_variableSet a variableAIdempotent
Create a Part Studio variable, or change its value if it already exists. By default
model with variables: put every key dimension (diameter, length, pitch, wall thickness,
...) in a variable first, then use '#name' wherever the size is needed, so changing one
value reshapes the whole model. Pass variables to set many in one call.
Inputs: element_id (required), document_id (required), kind, name, +4 more. Returns: object
shellShellA
Hollow out a part with walls of the given thickness. Give remove_face_ids to leave
those faces open (a box without a lid, a cup, an enclosure) or hollow_part_ids to hollow a
part completely and leave a closed void inside - exactly one of the two. The walls grow
inward by default; opposite_direction grows them outward from the original surface.
Example: a 40 x 30 x 20 mm box (24 000 mm3) shelled to 2 mm walls with the top face removed
keeps 7 152 mm3. Use it instead of cutting an inner pocket by hand with extrude
(operation 'remove'); use boolean to combine or subtract whole parts. The face IDs come
from get_body_details. It appends one shell feature and returns its health plus
effect (parts and total volume before and after) and a warning when nothing changed:
Onshape can accept a feature that does nothing, so read it: a wall too thick for the part is
accepted as OK and changes nothing (a 50 mm wall on a 40 x 30 x 20 mm box answered OK with
the volume unchanged), and only that warning tells you. Remove it with delete_feature.
Inputs: thickness (required), element_id (required), document_id (required), name, +5 more. Returns: object
update_featureUpdate feature parametersAIdempotent
Change parameters of existing features (for example make an extrude deeper or a
fillet larger) without rebuilding them. Dependent features rebuild automatically. To
change several features at once pass updates: two requests in total, however many.
An automatically named extrude ('Extrude 8 mm') gets its name refreshed when its depth
changes (single-feature form).
Inputs: element_id (required), document_id (required), name, updates, +3 more. Returns: object
whoamiCheck Onshape connectionARead-only
Check that the configured credentials (API keys or OAuth sign-in) really work, by asking
Onshape which account they belong to: returns connected, user_id, name and the base_url in
use. Use it first in a session or whenever another tool answers 401, and to tell a wrong
key from a wrong document ID. Read-only, one request, nothing is changed. Onshape answers
200 with an empty body to credentials it does not recognise, so this call treats that
"anonymous" reply as a failure and explains how to fix the keys. It does not show which
permissions (read / write / delete) the key has - a 403 from a modeling tool means the key
lacks the write scope. For this server's own settings use get_settings.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 37 tools
Most tools target a clearly distinct resource+action (sketch, extrude, revolve, shell, fillet, chamfer, pattern, boolean, mate, variable, configuration), and the descriptions explicitly cross-reference alternatives (fillet vs chamfer, shell vs extrude-remove). The main friction is the three escape hatches — add_feature, add_custom_feature and onshape_api_request — plus update_feature, which all overlap in 'add/change arbitrary geometry'; the guidance differentiates them but an agent must read carefully to pick correctly.
Most tools follow a snake_case verb_noun pattern (list_documents, create_element, get_settings, set_variable, add_mate, update_feature, delete_feature). However, a large block of modeling tools is named after the bare feature (extrude, revolve, fillet, chamfer, shell, boolean, mirror), and there are further outliers like circular_pattern/linear_pattern (no verb) and whoami. Readable and intuitive by domain convention, but the conventions are genuinely mixed.
37 tools exceeds the comfortable range, and the surface spans modeling, assemblies, variables, configurations, custom features, export and two escape hatches. Most tools are distinct and earn their place in a real CAD workflow, but it is heavy enough that an agent faces a non-trivial selection problem each turn.
Coverage is strong: document/element lifecycle, the feature tree (sketch, extrude, revolve, patterns, mirror, boolean, shell, fillet, chamfer), parts and body inspection, assemblies and mates, variables and configurations, custom features, screenshots, export and raw API access. The notable gaps are deletion of documents and elements (explicitly admitted for documents), plus no drawing/version-management tools, which agents can partially work around via escape hatches.
Maintenance
Related MCP Connectors
Read, query, edit and render DWG drawings with AI. No AutoCAD required.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
Parametric 3D CAD for AI agents: build print-ready parts, check them, export STL, 3MF or STEP.
Text-to-CAD: build exact STEP or 3MF/STL on the server, each stated requirement measured.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to drive OnShape CAD through the REST API for parametric modeling, FeatureScript queries, and STL export/verification.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to drive Onshape CAD with 87 tools for documents, part studios, sketching, solid features, assemblies, drawings, measurement, and export, including zero-configuration browser sign-in.93156 npm7MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to create and modify real Onshape CAD models — sketches, extrudes, fillets, patterns, mates, and parametric variables — with every mutation returning structured status, warnings, and geometric deltas. Includes multi-view PNG rendering, image-reference decomposition, and drawing OCR so the agent can visually verify and iterate on parts and assemblies.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and edit native CAD parts and assemblies, inspect saved geometry and measurements, retain revisions, run mechanism and interference checks, and export STEP/STL/GLB artifacts through MCP tools.MIT