Connectors / Design
Design MCP connectors for Claude, ChatGPT and Cursor
5+ Design connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.
https://api.elaichi.ai/mcp
The same for every user.
-
Their own access. An agent never gets more than the person it acts for.
-
One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The connectors
Design connectors in the catalog
Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.
5 connectors
-
Aurora Solar API key 119 tools
-
Figma Bring your own OAuth app 45 tools
-
Miro Hosted sign-in 20 tools
-
Webflow Hosted sign-in 34 tools
-
Zeplin API key 121 tools
No Design connector by that name
It may sit under another category, or not be in the catalog yet — any documented API can become a connector.
In practice
What teams do with Design connectors
Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.
Design
-
Find every project a teammate can see
Ask which Zeplin projects and styleguides a specific person has access to before a handover, so nothing is left behind when work moves between designers.
-
Read the comment thread before a review
Ask for every open comment on a file and who left it, then walk into the review already knowing where the disagreements are.
-
See where a component or style is used
Before changing a button or a color, find out which pages use that component or class so nothing breaks on a page you forgot about.
Engineering
-
Read a prototype before the standup
Ask what a prototype on the board contains and how its screens connect, then create a new prototype from the agreed flow so the handoff is on the canvas, not in a chat.
-
Check a project's workflow statuses
Pull the workflow statuses your organization uses in Zeplin to confirm what "ready for development" actually means before picking up a screen.
-
Find the right component before building
Look up a component or component set by name, read its description, and confirm which file it lives in so the build matches the library.
Product
-
Get a snapshot of active projects
List every Zeplin project in the organization, read their descriptions and details, and update a project's description when scope changes after a planning session.
-
Leave feedback without opening the file
Post a comment on a specific frame in Figma from Claude while writing the spec, and react to a teammate's comment to show it has been seen.
-
Find the board from last quarter's kickoff
Search across boards by name or topic instead of scrolling through the dashboard. Pull up the roadmap board, read what is on the canvas, and summarize it for someone who missed the session.
IT
-
Deactivate a departing user the same day
Look up someone by name, deactivate their Aurora Solar user, and check that nothing was missed across teams before the offboarding ticket closes.
-
Remove a contractor's access at the end
See the external collaborators and members in your Zeplin organization, then remove a departing contractor from the projects they were on and from the organization itself.
-
Keep single sign-on settings current
Review the SSO providers configured on your Aurora Solar tenant and update a provider when your identity setup changes.
Once it is connected
Things to ask
Each of these is answered against the access the person asking already has, in the Design account you connected.
-
List Aurora Solar tenants with no active tenant users.
-
List the files in our Design System project.
-
Find the boards from last week's product kickoff
-
List the blog posts published this month on our marketing site
-
List Zeplin projects with no members added this month.
The tools
What an agent can call in Design
- Connectors
- 5+
- Tools
- 339
- Hosted sign-in
- 2
in the Design catalog
callable the moment you connect
connect with nothing to register
Of those 339 tools, 5% delete something. Restricting an agent to reads is not a promise here, it is 169 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.
- Read 50%
- 169 tools · list, get, search
- Write 27%
- 90 tools · create, update, send
- Delete 5%
- 18 tools · delete, remove, archive
- Other 18%
- 62 tools · vendor-specific verbs
One endpoint
https://api.elaichi.ai/mcp
Every connector above answers here.
Every Design connector, by depth
Tool counts are what the connector exposes today; the split is what those tools do.
Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect. API key and App credentials mean an admin pastes them once, with nothing to register.
| Connector | Tools | Read · write · delete | Sign-in |
|---|---|---|---|
| Zeplin | 121 | API key | |
| Aurora Solar | 119 | API key | |
| Figma | 45 | Your own app | |
| Webflow | 34 | Hosted | |
| Miro | 20 | Hosted |
FAQ
Frequently asked questions
How many Design connectors does Elaichi have?
5+ Design connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.
Can Claude, ChatGPT and Cursor all use Design connectors?
Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Design account once makes it reachable from every one of them.
Do Design connectors work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Design connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.
Do Design connectors need me to bring my own OAuth app?
Most do not. 2 of the Design connectors use Elaichi's hosted sign-in, with nothing to register. 2 connect with an API key or app credentials that an admin pastes once, with no app to register. 1 asks you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.
Can I stop an agent from writing to Design tools?
Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Design connector is a matter of allowing the reads and leaving the writes out.
Put Design connectors in front of your team
14 days on Gold, no credit card. Connect one and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.