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.
- OAuth or API key
- Free 14-day trial
- No credit card
Summarize what changed in the bracket assembly since last week.
Working in Onshape with Elaichi
-
Onshape purchases list plan purchases
-
List all Onshape purchases
-
List all Onshape aliases
How to connect Onshape to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Onshape MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Onshape MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Onshape through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Onshape is logged.
-
Design
Catch up on a document after a review
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.
-
Engineering
Find the right part across documents
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.
-
Manufacturing
Pull release details for the shop floor
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.
-
Product management
Report on what shipped this sprint
Draft a weekly update from the Onshape documents and versions touched by the team, with release status and open work listed in one place.
-
Procurement
Track plan purchases and seats
List the Onshape plan purchases the company holds, see which have been consumed and cancel the ones nobody uses before the next renewal.
-
IT
Keep team aliases tidy
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.
Try asking
- “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.”
What connecting Onshape gets you
6 screens from Elaichi, each doing one job for your Onshape account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any Onshape document in plain words.
Three starter prompts pull live answers from Onshape documents, aliases and purchases.
Copy the endpoint
AI apps
One Onshape endpoint for every MCP client.
Claude, ChatGPT and Cursor connect through one governed endpoint, no SDK, no shared API key.
Tool catalog
304 Onshape tools, ready without writing code.
Documents, parts, assemblies, aliases and purchases are covered, each with its resources and methods.
Toolboxes
Each team gets its own Onshape toolbox.
Design, manufacturing and procurement each see the Onshape tools their work calls for.
Shared connections
Teammates use Onshape without ever seeing a credential.
One person connects Onshape, shares it with teams, and nobody else handles a secret.
Audit log
Every Onshape action is logged with a name.
When, who, what happened and which document, in an append-only audit log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Onshape digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch documents
Onshape
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Onshape
Queued
Workflows
A schedule starts Onshape work end to end.
Released documents are fetched, grouped, drafted into a digest, approved by a person, posted back.
Onshape health
Refreshed 4 minutes ago · every 15 minutes · from the documents collection
Documents
1,284 ↓ 12%
Aliases
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Documents created
Last 14 days
By team
Share of activity
Design 34%
Mechanical engineering 27%
Manufacturing 21%
Product 18%
Collections and dashboards
Onshape health numbers arrive without anyone asking.
Four metrics, fourteen days of documents created and a team breakdown, refreshed on a schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Onshape tools for your AI agents
304 tools are ready to call through Elaichi's MCP endpoint the moment you connect Onshape, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Onshape in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot