MCP server for Zeplin - used for screen and component code generation 💻
If you already use Zeplin For AI, the zeplin for ai mcp server is the piece that lets your assistant work with it directly. MCP server for Zeplin - used for screen and component code generation 💻.
Connect AI agents like Cursor, Windsurf, and VS Code (w/ Copilot) to Zeplin. Using the MCP server, AI agents can tap into:
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Documentation — ** Annotations added to screens that provide extra context, like how things should behave or tips for implementation — letting the agent go beyondBenefit — ** Each request to the Zeplin MCP server will fetch a smaller, more focused dataset, making it easier to stay within context limits and allowing theConfiguration is passed through the environment: ZEPLIN_ACCESS_TOKEN, YOUR_ZEPLIN_PERSONAL_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at @zeplin/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Zeplin For AI's toolset — Documentation, Benefit — is a fair guide to whether it matches your workflow. It is maintained by zeplin; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Documentation | ** Annotations added to screens that provide extra context, like how things should behave or tips for implementation — letting the agent go beyond static visuals and build real interactions. |
| Benefit | ** Each request to the Zeplin MCP server will fetch a smaller, more focused dataset, making it easier to stay within context limits and allowing the model to concentrate on one piece at a time. |
{
"mcpServers": {
"server-zeplin": {
"command": "npx",
"args": ["-y", "@zeplin/mcp-server"],
"env": {
"ZEPLIN_ACCESS_TOKEN": "your-value",
"YOUR_ZEPLIN_PERSONAL_ACCESS_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ZEPLIN_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_ZEPLIN_PERSONAL_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.