Blender integration through the Model Context Protocol
Onshape is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Drive Onshape CAD from an assistant: documents, sketches, solid features, assemblies and exports.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user gpambrozio-onshape-mcp '--' npx -y @gpambrozio/onshape-mcp
# 2 — ask your agent for something these tools do
# onshape_create_assembly, onshape_get_assembly, onshape_insert_instance and 84 more
Onshape costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Onshape as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user gpambrozio-onshape-mcp '--' npx -y @gpambrozio/onshape-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take ONSHAPE_ACCESS_KEY (Onshape API access key. Optional: the server signs in through the browser when this is not set.), ONSHAPE_SECRET_KEY (Onshape API secret key, paired with ONSHAPE_ACCESS_KEY.), ONSHAPE_MCP_OUTPUT_DIR (Directory for exported STL/STEP files and renders. Defaults to the working directory.) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
87 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Add an assembly tab to a workspace.
No parameter schema on file.
The assembly's instances, occurrences, mate features and mate connectors.
No parameter schema on file.
Insert a part, a whole Part Studio or another assembly into an assembly. Insert from a version when pulling
No parameter schema on file.
Remove one instance from an assembly by its occurrence node id.
No parameter schema on file.
Apply a 4x4 row-major transform (16 numbers, metres) to the given occurrence paths.
No parameter schema on file.
The mates, mate connectors and groups defined in an assembly, with their feature ids.
No parameter schema on file.
Place an implicit mate connector on an instance by inference (CENTROID, TOP, ...). Its feature id is what
No parameter schema on file.
Join two or more mate connectors with a mate: FASTENED, REVOLUTE, SLIDER, PLANAR, and so on.
No parameter schema on file.
Lock several instances together without individual mates.
No parameter schema on file.
Post a hand-written assembly feature payload — the escape hatch for mate types with no tool here.
No parameter schema on file.
The assembly's BOM table.
No parameter schema on file.
Mass, volume, centroid and inertia for a whole assembly.
No parameter schema on file.
Sign in to Onshape by opening a browser. method='api_key' (default) opens a local page that links to the
No parameter schema on file.
Wait for, and report on, the login started by onshape_login. Call this repeatedly while the user is in the
No parameter schema on file.
Store an Onshape access key and secret key directly, without a browser. Use when the user already has a key
No parameter schema on file.
Report which Onshape credential is active, where it came from and whether it still works. Secrets are redacted.
No parameter schema on file.
Delete the credential this server stored (keychain entry and config file). Credentials coming from
No parameter schema on file.
List documents visible to the signed-in user, most recently modified first.
No parameter schema on file.
Find documents by name. Search before creating, so repeated runs do not make duplicates.
No parameter schema on file.
Read one document's metadata, including its default workspace id.
No parameter schema on file.
Document metadata plus every workspace and the elements (tabs) inside each — the fastest way to orient in an
No parameter schema on file.
Create a document. Free Onshape accounts may only create public documents, so pass public=true there. The
No parameter schema on file.
Change a document's name or description.
No parameter schema on file.
Move a document to the trash. This affects the whole document, not a single tab.
No parameter schema on file.
List a document's workspaces (branches).
No parameter schema on file.
List the elements (tabs) in a workspace: Part Studios, assemblies, drawings, Feature Studios.
No parameter schema on file.
List the Part Studios in a workspace, optionally filtered by a substring of the name.
No parameter schema on file.
List the immutable versions of a document, newest first.
No parameter schema on file.
Snapshot the workspace as an immutable version. Do this before restructuring an existing design: it is the
No parameter schema on file.
Delete one element (tab) from a workspace.
No parameter schema on file.
Create a drawing of a part, Part Studio or assembly. The source must be referenced by version — call
No parameter schema on file.
The views placed on a drawing sheet.
No parameter schema on file.
Export a drawing as PDF (or DWG/DXF) through the translation service.
No parameter schema on file.
Export the Part Studio as STL, for 3D printing. Measure the model before exporting it.
No parameter schema on file.
Export through Onshape's translation service: STEP, IGES, 3MF, PARASOLID, SOLIDWORKS and others. Slower than
No parameter schema on file.
Render the element server-side and return the image. Unlike a thumbnail this is generated on demand, so it
No parameter schema on file.
Save Onshape's stored thumbnail. Thumbnails are generated asynchronously and lag edits — prefer
No parameter schema on file.
The thumbnail sizes Onshape has rendered for this element, with their hrefs.
No parameter schema on file.
Extrude the closed regions of a sketch into a solid. op=NEW makes a body, ADD merges into existing bodies,
No parameter schema on file.
Extrude a sketch as a cut (op=REMOVE). Sketch a circle first, then cut it through the body.
No parameter schema on file.
Give a sketch region a wall thickness instead of a solid depth.
No parameter schema on file.
Revolve a sketch profile around an axis. With no axis given, the sketch's own construction line is used
No parameter schema on file.
Sweep the closed regions of one sketch along the edges of another.
No parameter schema on file.
Round the selected edges. Name the edges with one of: edges (ids), query (FeatureScript), feature (every edge
No parameter schema on file.
Bevel the selected edges. Selection works exactly as for onshape_fillet.
No parameter schema on file.
Hollow the body out to a wall thickness, removing the selected faces to open it.
No parameter schema on file.
Taper faces away from a neutral plane — the usual requirement for moulded or cast parts.
No parameter schema on file.
Combine bodies: UNION, SUBTRACTION or INTERSECTION. Subtraction also needs the targets query.
No parameter schema on file.
Merge all modifiable solid bodies into one. The usual cleanup before exporting a single part.
No parameter schema on file.
Mirror parts, bodies or faces across a plane.
No parameter schema on file.
Repeat geometry along a direction, at a fixed spacing.
No parameter schema on file.
Repeat geometry around an axis.
No parameter schema on file.
Add a construction plane offset from a default plane, a face, or another plane.
No parameter schema on file.
Add a Feature Studio tab for custom FeatureScript.
No parameter schema on file.
The FeatureScript source of a Feature Studio.
No parameter schema on file.
Replace the FeatureScript source of a Feature Studio. The whole file is overwritten.
No parameter schema on file.
The feature specifications a Feature Studio defines, for calling its custom features.
No parameter schema on file.
Every edge of every solid body, with its deterministic id, owning body, type and radius (inches).
No parameter schema on file.
Circular edges, optionally only those matching a radius — the usual way to pick hole rims to fillet.
No parameter schema on file.
Deterministic ids of the edges a given feature created, evaluated by Onshape.
No parameter schema on file.
Read the properties of an element, or of one part when part is given.
No parameter schema on file.
Write properties such as part number, description or material. Only editable properties are accepted; read
No parameter schema on file.
Add a Part Studio tab to a workspace. The new element id is at result.response.id.
No parameter schema on file.
The full feature tree with each feature's id, type, parameters and regeneration state. Large — prefer
No parameter schema on file.
The parameter ids, enum names and defaults Onshape expects for every feature type in this Part Studio. Read
No parameter schema on file.
Entities and solved geometry for every sketch in a Part Studio, or for one sketch.
No parameter schema on file.
Bodies, faces and edges with their deterministic ids — the source for explicit edge selection.
No parameter schema on file.
The parts a Part Studio produces, with part ids for export and assembly insertion.
No parameter schema on file.
Volume, mass, centroid and inertia for the Part Studio's bodies.
No parameter schema on file.
Body count, overall bounding box in inches and total volume. Use this to check a model matches its intended
No parameter schema on file.
Count parts and bodies, and fail when the counts do not match the expectations you pass. A cheap regression
No parameter schema on file.
Post a hand-written BTM feature payload to a Part Studio. The escape hatch for feature types this server has
No parameter schema on file.
Replace an existing feature's payload, e.g. to change a dimension. Post the whole feature JSON.
No parameter schema on file.
Remove one feature from the tree. Features added after it may fail to regenerate.
No parameter schema on file.
Set the rollback index so features after it are suppressed. Index 0 rolls back to before the first feature.
No parameter schema on file.
Run a FeatureScript function against the Part Studio and return its decoded value. The general-purpose way
No parameter schema on file.
Make an authenticated request to an arbitrary Onshape REST endpoint, for anything the dedicated tools do not
No parameter schema on file.
Add a sketch holding one closed rectangle, ready to extrude. Corners are opposite, in inches.
No parameter schema on file.
Add a sketch holding one circle.
No parameter schema on file.
Add a sketch holding one line segment. A line alone encloses no region, so it cannot be extruded.
No parameter schema on file.
Add a sketch with a circle profile and a construction line. onshape_revolve spins the profile around that
No parameter schema on file.
Add a sketch from a list of entities: lines, circles, rectangles and arcs. Use this when the single-shape
No parameter schema on file.
Add a sketch of a straight stem joined to a hooked arc, approximated by segments — a ready-made path for
No parameter schema on file.
The variable table of a Part Studio: names, expressions and descriptions.
No parameter schema on file.
Create or update a variable. Feature tools can then reference it by name (depth_variable, radius_variable,
No parameter schema on file.
The configuration parameters an element exposes, with their ids and allowed values.
No parameter schema on file.
Turn configuration parameter values into the encoded string other tools accept as configuration.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Onshape or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Onshape can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.