mcp-server

Zeplin MCP Server

Zeplin design data becomes available to coding agents for UI implementation and review. Developers can retrieve component and screen specifications, inspect annotations and design tokens, and download layer assets for their codebase.

Server facts

mcp-server

Project

Author
zeplin
License
MIT

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
10
Last commit
Data as of

Tags

  • mcp server
  • ui implementation
  • zeplin

Overview

Zeplin’s component specifications, screen layouts, and implementation notes give coding agents design context for UI work. The get_component tool retrieves a reusable element’s properties, variants, layers, and related tokens, while get_screen supplies screen structure, positioning, styling, annotations, and project tokens. Developers can use these details when adapting existing interfaces or building components before assembling a larger screen. Screen annotations add behavioral guidance alongside visual specifications, and get_design_tokens retrieves tokens from a project or styleguide for reference during implementation.

When a design references an asset missing from the codebase, download_layer_asset can fetch the selected layer’s visual asset and save it locally. For larger designs, get_screen supports narrowing requests to the linked screen version with includeVariants set to false, or concentrating on a named layer through targetLayerName. These options support focused requests when extensive design data could strain an agent’s context window. The integration connects Zeplin with clients such as Cursor, Windsurf, and VS Code with Copilot, using a Zeplin personal access token.

mcp-server setup notes

  • mcp-server records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers