Addressing is by the link a designer already sent: get_screen and get_component both take a Zeplin URL, and get_design_tokens takes a resource id for the project or styleguide. Annotations come down with the screen, so interaction notes written in Zeplin reach the code without a second trip. download_layer_asset is the only call that writes to disk, and it exists for assets a design references but the repository is missing.
Zeplin's own server, turning a design URL into the structure and tokens a developer needs to build the thing.
- Component specifications from a URL: properties, variants, layers and the design tokens attached to them.
- Screen data from a URL: screen variants, layer structure with position and styling, annotations, and project-level tokens, narrowed to one layer with targetLayerName when the screen is large.
- Design tokens for a whole project or styleguide by resource id.
- Asset download to a local path — an SVG icon or PNG image behind a layer — for the case where the design references it and the codebase does not have it.
The Zeplin URL of the screen or component you are building, the resource id of the project or styleguide whose tokens you want, and a local path for anything you download.
One command plus a key — npx @zeplin/mcp-server@latest, then supply credentials