# Design MCP connectors for Claude, ChatGPT and Cursor 5+ Design connectors in the Elaichi catalog, each callable through https://api.elaichi.ai/mcp once connected, under the same roles, restrictions and audit log as the rest of the catalog. Source: https://elaichi.ai/connectors/category/design/ | | | | --- | --- | | Category | Design | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | ## Design connectors - [Aurora Solar](https://elaichi.ai/connectors/aurorasolar/) — 119 tools · API key - [Figma](https://elaichi.ai/connectors/figma/) — 45 tools · bring your own OAuth app - [Lucid](https://elaichi.ai/connectors/lucid/) — hosted sign-in - [Magic Patterns](https://elaichi.ai/connectors/magic-patterns/) — 23 tools · hosted sign-in - [Miro](https://elaichi.ai/connectors/miro/) — 20 tools · hosted sign-in - [Moda](https://elaichi.ai/connectors/moda/) — hosted sign-in - [Webflow](https://elaichi.ai/connectors/webflow/) — 34 tools · hosted sign-in - [Whimsical](https://elaichi.ai/connectors/whimsical/) — 17 tools · hosted sign-in - [Zeplin](https://elaichi.ai/connectors/zeplin/) — 121 tools · API key ## What teams do with Design connectors ### Design - **Find every project a teammate can see** (Zeplin) — 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** (Figma) — 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** (Webflow) — 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 - **Pull generated files straight into the codebase** (Magic Patterns) — Read the files behind an artifact, write changes back, and publish when it is ready to share with the rest of the team. - **Read a prototype before the standup** (Miro) — 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. - **Diagram the system before the review** (Whimsical) — Hand over the service names and how they talk to each other, and the agent draws the architecture diagram and tidies the layout. Change a dependency later and ask it to redraw the affected part. ### Product - **Summarize a user flow before the review** (Lucid) — Ask for the checkout flow diagram and get the steps, branches and open questions written out, so the review starts with everyone on the same page. - **Get a snapshot of active projects** (Zeplin) — 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** (Figma) — 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. ### Marketing - **Turn one campaign design into every size** (Moda) — Ask for the launch design to be resized for Instagram, LinkedIn, email and the website, and have each version saved back in Moda ready to review. - **Grab a frame for the launch post** (Figma) — Ask for an image of a named frame in Figma and drop it into release notes or a campaign brief without exporting by hand. - **Summarize this week's form submissions** (Webflow) — Pull every contact and demo request that came through your Webflow forms and get them grouped by campaign, with the ones that need a reply called out. ## Things to ask once it is connected - "List Aurora Solar tenants with no active tenant users." (Aurora Solar) - "List the files in our Design System project." (Figma) - "Summarize the checkout flow diagram and list the decision points." (Lucid) - "Create a pricing page design using our main design system." (Magic Patterns) - "Find the boards from last week's product kickoff" (Miro) - "Resize the spring launch design for Instagram, LinkedIn and email." (Moda) - "List the blog posts published this month on our marketing site" (Webflow) - "Turn the onboarding spec into a flowchart in the Product workspace" (Whimsical) ## What an agent can call in Design 379 tools across the category. Of these connectors, 6 use hosted sign-in with nothing to register first; 2 connect with an API key or app credentials an admin pastes once; 1 asks you to bring your own OAuth app. ## 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. 6 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. ### Whose access does an agent get on a shared Design connection? The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential. [Browse the full connector catalog](https://elaichi.ai/connectors/)