Integration

Zeplin integration

Design handoff and collaboration platform API. Access projects, screens, components, and style guides. Bridge between design and development teams. Essential for design systems, developer handoff, and design collaboration.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Zeplin.Built from the 11 Zeplin tools below, on the connection you add once.

Common Zeplin use cases

  • design system
  • design review
  • developer handoff
  • design specs
  • project view
  • color palette
  • screen catalog
  • component specs
  • design feedback
  • project overview

What you can do with Zeplin

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Component, 2 operations

  • get_componentGet componentGETRetrieves detailed information about a component.
  • list_componentsList componentsGETLists all components in a Zeplin project.

Project, 2 operations

  • get_projectGet projectGETRetrieves detailed information about a Zeplin project.
  • list_projectsList projectsGETLists all projects in Zeplin.

Screen, 2 operations

  • get_screenGet screenGETRetrieves detailed information about a screen.
  • list_screensList screensGETLists all screens in a Zeplin project.

Color, 1 operation

  • get_styleguide_colorsGet styleguide colorsGETLists all colors in a style guide.

Note, 1 operation

  • list_screen_notesList screen notesGETLists all notes/comments on a screen.

Styleguide, 1 operation

  • list_styleguidesList styleguidesGETLists all style guides in Zeplin.

Text style, 1 operation

  • get_styleguide_text_stylesGet styleguide text stylesGETLists all text styles in a style guide.

Version, 1 operation

  • get_screen_versionsGet screen versionsGETLists version history for a screen.

Zeplin API rate limits

  • 200 requests per minute

Rate limits vary by plan

These are the limits Zeplin documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Zeplin documentation for current values.

Use Zeplin from Claude Code, Cursor or Codex

Connect Zeplin in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Zeplin operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Zeplin

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Zeplin once

    Add your Zeplin connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Zeplin integration FAQ

What can you do with the Zeplin integration?

LiveContext exposes 11 operations on Zeplin, covering component, project, screen and color. Common uses include design system, design review and developer handoff.

What are the Zeplin API rate limits?

Zeplin documents 200 requests per minute. Rate limits vary by plan Limits are set by Zeplin and can depend on your plan.

Popular integrations

Browse the whole catalog