# Onshape MCP connector

The Onshape connector brings documents, parts, assemblies, aliases and plan purchases to Claude, ChatGPT, Cursor and Microsoft Copilot through one governed endpoint, where every request runs as the person who signed in and lands in an audit log.

Source: https://elaichi.ai/connectors/onshape/

## Facts

| | |
| --- | --- |
| Application | Onshape |
| Category | Product Development |
| AI tools | 304 |
| Authentication | OAuth or API key |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Onshape is connected

- Summarize what changed in the bracket assembly since last week.
- List every team alias and who belongs to each.
- Show our plan purchases and which ones are still unused.

## Connect Onshape in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Onshape.
2. Optionally set Share with, then press Connect.
3. Supply your own Onshape app, then approve. Onshape needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Onshape tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Onshape MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Onshape MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Onshape MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Onshape MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Onshape MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Onshape to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Onshape tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Onshape through Elaichi

### Catch up on a document after a review

Design. Ask what changed in an assembly since the last design review and get a plain summary of the parts and versions involved, without opening every tab in Onshape.

### Find the right part across documents

Engineering. Describe the part you remember and have the agent locate the Onshape document, workspace and version that holds it, then pull its properties into the conversation.

### Pull release details for the shop floor

Manufacturing. Check which drawings and parts have been released, who released them and when, so the floor works from the version that is actually approved in Onshape.

### Report on what shipped this sprint

Product management. Draft a weekly update from the Onshape documents and versions touched by the team, with release status and open work listed in one place.

### Track plan purchases and seats

Procurement. List the Onshape plan purchases the company holds, see which have been consumed and cancel the ones nobody uses before the next renewal.

### Keep team aliases tidy

IT. Create and update Onshape aliases as teams change, review who belongs to each one and retire aliases that no longer map to a real group.

## Elaichi vs Zapier MCP vs Composio for Onshape

All three can connect Onshape to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Onshape tools | Allow or restrict single Onshape tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Onshape call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Onshape to Claude?

Connect Onshape in Elaichi first, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. Onshape asks you to register an OAuth application inside your Onshape account, so one person brings that client ID and secret to Elaichi once, or pastes an Onshape API key instead. After that, each person signs in to Onshape as themselves and nobody else touches a credential.

### Does Onshape work with ChatGPT and Cursor as well as Claude?

Yes. The Onshape connection you set up in Elaichi is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Onshape once and every client sees it.

### What can an AI agent actually do with my Onshape data?

It can find Onshape documents, parts, assemblies and drawings, read their versions and properties, summarize what changed, and update items such as team aliases and app elements when you ask. It can also list and manage Onshape plan purchases. Short, concrete asks such as naming the document and the version work better than long paragraphs.

### Does connecting Onshape give the AI access to every document in my workspace?

No. Every request to Onshape runs as the person who signed in, so the agent sees only the documents, folders and teams that person can already open in Onshape. Elaichi can narrow that access with roles and restrictions, and it can never widen it beyond what Onshape itself allows.

### Can my team share one Onshape connection?

Yes. One person connects Onshape in Elaichi and shares the connection with a team, and nobody else on that team handles the OAuth application or an API key. Each person still signs in as themselves, so the audit log names the engineer who opened or changed an Onshape document, not the person who set up the connection.

### Can I stop an agent from deleting or changing things in Onshape?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Onshape documents while restricting deletes of aliases, purchases or app elements, on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Onshape connection when someone leaves?

Offboarding that person in Elaichi ends their access to Onshape through every client at once. A shared Onshape connection keeps working for everyone else on the team. If you disconnect Onshape in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the Onshape MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Onshape is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Onshape?

Yes. Both let Claude, ChatGPT or Cursor use Onshape. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Onshape call.

### How is Elaichi different from Composio for Onshape?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Onshape: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 304 Onshape tools

Every tool below is callable through https://api.elaichi.ai/mcp once Onshape is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Onshape purchases list plan purchases** (List). Get a list of all app purchases made for the specified plan. Required: planId. Paginated with offset/limit (max 20 per page).
- **List all Onshape purchases** (List). Get a list of all app purchases made by the current user. This API should be used within the context of an OAuth-enabled application.
- **Onshape purchases consume purchase** (Action). Mark a purchase as consumed by the current user. Required: pid.
- **Onshape purchases cancel purchase new** (Cancel). Cancel a recurring subscription for the specified account ID and purchase ID. Required: aid, pid.
- **List all Onshape aliases** (List). Get a list of all aliases that exist for your enterprise. Paginated with offset/limit (max 20 per page).
- **Create a Onshape alias** (Create). Create an alias in your enterprise. Manage users and teams global permission is required to call this API.
- **Get single Onshape alias by ID** (Get). Get an alias by ID. Get the information for an alias ID. The id is the id (alias id, or account id for purchases). Required: id.
- **Update a Onshape alias by ID** (Update). Add, remove, replace, or rename entries in an alias list. Manage users and teams global permission is required to call this API. Add new users in the additions array. Remove existing users in the removals array. Attempts to remove a user that does not exist in the Alias list will have no effect. Replace the entire Alias list with the entries array. The id is the id (alias id, or account id for purchases). Required: id.
- **Delete a Onshape alias by ID** (Delete). Delete an alias from your enterprise. Manage users and teams global permission is required to call this API. The id is the id (alias id, or account id for purchases). Required: id.
- **Onshape aliases list members** (List). Get all users and teams assigned to an alias. This is a search-like endpoint that returns a subset of the member list. Use getAlias to return all members every time it's called. Required: aid. Paginated with offset/limit (max 20 per page).
- **Onshape app elements create element** (Create). Create a new application element. See API Guide: Structured Storage for more information. Required: did, wid, formatId.
- **Onshape app elements bulk create** (Create). Create multiple empty application elements at once. Call this faster API instead of creating multiple app elements one at a time or in parallel. Required: did, wid, formatId.
- **Onshape app elements download blob subelement workspace** (Download). Download the blob element (i.e., a file) stored in an app element in a document's workspace. The downloaded file can be used to retrieve stored subelements. Required: did, wid, eid, bid.
- **Onshape app elements upload blob subelement** (Upload). Create a new blob subelement from an uploaded file. The file is sent as multipart form data. Required: did, wid, eid, bid.
- **Onshape app elements delete blob subelement** (Delete). Delete a blob subelement from an app element. Required: did, wid, eid, bid.
- **Onshape app elements get transactions** (Get). Get a list of all transactions performed on an element. Required: did, eid, wid.
- **Onshape app elements start transaction** (Start). Start a transaction. Creates a microbranch (i.e., a branch for a new microversion). Required: did, eid, wid.
- **Onshape app elements abort transaction** (Action). Abort a transaction. Deletes a microbranch (i.e., the branch with the microversion for the transaction). Required: did, eid, wid, tid.
- **Onshape app elements commit transactions** (Action). Merge multiple transactions into one microversion. If successful, all transactions will be committed to a single microversion. If the call raises an error, nothing will be committed. Required: did, wid.
- **Onshape app elements download blob subelement** (Download). Download a blob subelement from the specified app element. Download a blob subelement as a file. Required: did, vm, vmid, eid, bid.
- **Onshape app elements get blob subelement IDS** (Get). Get a list of all blob subelement IDs for the specified workspace, version, or microversion. Required: did, eid, wvm, wvmid.
- **Onshape app elements compare JSON** (Action). Compare app element JSON trees between workspaces/versions/microversions in a document. Specify the source workspace/version/microversion in the URL and specify the target workspace/version/microversion in the query parameters. Required: did, wvm, wvmid, eid.
- **Onshape app elements get sub content** (Get). Get a list of all subelement IDs in a specified workspace/version/microversion. Required: did, wvm, wvmid, eid.
- **Onshape app elements update app element** (Update). Update the content for the specified app element. See API Guide: Structured Storage for more information. Required: did, eid, wvm, wvmid.
- **Onshape app elements get history** (Get). Get the history of the specified all element. Required: did, eid, wvm, wvmid.
- **Onshape app elements get subelement IDS** (Get). Get a list of all subelement IDs in a specified workspace/version/microversion. Required: did, eid, wvm, wvmid.
- **Onshape app elements get JSON** (Get). Get the full JSON tree for the specified workspace/version/microversion. Required: did, wvm, wvmid, eid.
- **Onshape app elements get JSON paths** (Get). Get the JSON at specified paths for an element. Use this endpoint to return the JSON at the specified path instead of returning the entire JSON for the element. This POST endpoint does not write any information. Required: did, wvm, wvmid, eid.
- **Onshape app elements get sub content batch** (Get). Get a list of multiple subelements by document ID, workspace or version or microversion ID, tab ID, and subelement IDs. Required: did, wvm, wvmid, eid.
- **Onshape app elements delete content batch** (Delete). Delete multiple subelements array by document ID, workspace or version or microversion ID, tab ID, and subelement IDs. Required: did, eid, wvm, wvmid.
- **Onshape app elements delete content** (Delete). Deletes the content from the specified app element. Required: did, eid, wvm, wvmid, sid.
- **Onshape app elements create reference** (Create). Creates a reference to an app element. Required: did, eid, wvm, wvmid.
- **Onshape app elements resolve reference** (Action). Resolves a single reference to an app element. For single operations only. Use resolveReferences for bulk operations. Required: did, eid, wvm, wvmid, rid.
- **Onshape app elements update reference** (Update). Update an app element reference. Required: did, eid, wvm, wvmid, rid.
- **Onshape app elements delete reference** (Delete). Delete an app element reference. Required: did, eid, wvm, wvmid, rid.
- **Onshape app elements resolve references** (Action). Resolves bulk app element references. For bulk operations only. Use resolveReference for a single operation. Required: did, wvm, wvmid, eid.
- **Onshape app elements resolve all references** (Action). Resolves bulk app element references. Resolve all references for all workspace elements. For bulk operations only. Use resolveReferences for a single element. Required: did, wvm, wvmid.
- **Onshape app associative data copy associative data** (Copy). Copy associative data from one view to another. You can manage associativity with translateIds. Required: did, wid, eid.
- **Onshape app associative data get associative data** (Get). Get the associative data for the specified app element. You can manage associativity with translateIds. Required: did, wvm, wvmid, eid.
- **Onshape app associative data post associative data** (Action). Set the associative data for the specified app element. You can manage associativity with translateIds. Required: did, eid, wvm, wvmid.
- **Onshape app associative data delete associative data** (Delete). Delete the associative data from the specified app element. You can manage associativity with translateIds. Required: did, eid, wvm, wvmid.
- **Onshape applications get company app settings** (Get). Get company-level preference settings for an application. This API is only usable with an OAuth token and only by the current user or admin. Required: cpid, cid.
- **Onshape applications update app company settings** (Update). Update company preference settings for an application. This API is only usable with an OAuth token and only by the current user or admin. Add or update a setting identified by key with value. Operation and field may optionally be specified when updating Map type settings. Field specifies the key of the setting Map to update. Required: cpid, cid.
- **Onshape applications delete company app settings** (Delete). Delete a company's application preference settings. This API is only usable with an OAuth token and only by the current user or admin. Required: cpid, cid.
- **Onshape applications get user app settings** (Get). Get user-level preference settings for an application. This API is only usable with an OAuth token and only by the current user or admin. Required: uid, cid.
- **Onshape applications update app settings** (Update). Update a user's application preference settings. This API is only usable with an OAuth token and only by the current user or admin. Add or update a setting identified by key with value. Operation and field may optionally be specified when updating Map type settings. Field specifies the key of the setting Map to update. Required: uid, cid.
- **Onshape applications delete app settings** (Delete). Delete a user's application preference settings. This API is only usable with an OAuth token and only by the current user or admin. Required: uid, cid.
- **Onshape applications get applicable extensions for client** (Get). Get a list of the client extensions the specified user has granted/accepted terms for. Required: uid, cid.
- **Onshape assemblies get named views** (Get). Get the view data for all named views for the specified element. Required: did, eid.
- **Onshape assemblies create assembly** (Create). Create a new assembly tab in the document. Required: did, wid.
- ...and 254 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
