Zeplin MCP connector
The Zeplin connector brings your Zeplin organizations, projects, members, styleguides, and workflow statuses to Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so each person can review and manage them inside their own Zeplin access with every action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
List Zeplin projects with no members added this month.
Working in Zeplin with Elaichi
-
List all Zeplin me
-
List all Zeplin organizations
-
Get single Zeplin organization by ID
How to connect Zeplin to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Zeplin 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.
Zeplin 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.
Zeplin 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.
Zeplin 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.
Zeplin 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 Zeplin 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 Zeplin through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Zeplin is logged.
-
Design ops
Onboard a new designer to the right projects
Add a new hire as a Zeplin member and put them on the projects their squad works in, all from one request instead of clicking through each project.
-
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.
-
Engineering
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.
-
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.
-
IT
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.
-
Engineering
Set up notifications when projects change
Create or adjust a Zeplin organization webhook so your build or chat tools hear about changes without anyone watching the project page.
Try asking
- “List Zeplin projects with no members added this month.”
- “Which members belong to more than five Zeplin projects?”
- “Summarize our Zeplin organization seats and billing plan.”
What connecting Zeplin gets you
6 screens from Elaichi, each doing one job for your Zeplin account.
Ask Elaichi to work across your apps.
List Zeplin projects with no members added this month.
Which members belong to more than five Zeplin projects?
Summarize our Zeplin organization seats and billing plan.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Zeplin projects in plain language.
Starter prompts return answers from live Zeplin projects, members and organizations.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Zeplin here.
One governed MCP endpoint for Zeplin over OAuth, no SDK, no shared API key.
Tool catalog
121 Zeplin tools are ready to call.
Projects, members, organizations and billing methods are cataloged, with no custom code written.
Toolboxes
Every team gets its own Zeplin toolbox.
Design, product and engineering each see a curated set of Zeplin tools.
Shared connections
Teammates use Zeplin accounts without credentials.
The connections table shows who connected each Zeplin account and its shared teams.
Audit log
Every Zeplin call is answered for.
When, who, what happened, type and resource, appended for every Zeplin call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Zeplin digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Zeplin
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
Zeplin
Queued
Automations
A schedule drafts your Zeplin project digest.
Six steps fetch and group Zeplin projects, draft a digest, then post on approval.
Zeplin health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Members
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Design EMEA 34%
Product 27%
Mobile apps 21%
Web platform 18%
Collections and dashboards
Zeplin project health arrives already counted.
Four metrics, 14 days of projects created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Zeplin
All three can connect Zeplin 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 Zeplin tools | Allow or restrict single Zeplin 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 Zeplin 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.
Zeplin tools for your AI agents
121 tools are ready to call through Elaichi's MCP endpoint the moment you connect Zeplin, 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 Zeplin to Claude?
First, connect Zeplin in Elaichi by pasting a Zeplin API key, which takes about a minute. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in Zeplin and no client ID or secret to generate.
Does Zeplin work with ChatGPT and Cursor as well as Claude?
Yes. Once Zeplin is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Zeplin once and every client picks it up.
What can an AI agent actually do with my Zeplin data?
It can list your Zeplin organizations, projects, styleguides, members, and workflow statuses, look up a single project or organization, and update a project's details. It can also add or remove members and project members, check organization billing, and create or update organization webhooks. Because Zeplin exposes many actions, short concrete asks such as "list the projects Maria can see" work better than long instructions.
Does connecting Zeplin give the AI access to every project in my workspace?
No. Every request runs as the person who signed in, so the AI sees only the Zeplin organizations, projects, and styleguides that person already has access to. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Zeplin itself allows that person.
Can I stop an agent from deleting or changing things in Zeplin?
Yes. Restrictions in Elaichi work per action, so you can allow reading Zeplin projects and members while restricting removing members or updating projects and webhooks. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
What happens to a Zeplin connection when someone leaves?
Offboarding a person in Elaichi ends their access to Zeplin through every AI client at once. A Zeplin connection shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting Zeplin once in Elaichi removes it from every client at the same time.
Does the Zeplin MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Zeplin 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 Zeplin?
Yes. Both let Claude, ChatGPT or Cursor use Zeplin. 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 Zeplin call.
How is Elaichi different from Composio for Zeplin?
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 Zeplin: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Zeplin 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