Skip to main content
Glama
zeplin

Zeplin MCP Server

Official
by zeplin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Zeplin MCP Server

No user-submitted related servers found.

    Related Servers

    • Sunnyside Figma MCP

      tercumantanumut
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Figma designs to AI agents, enabling extraction of production-ready code, assets, and design tokens through natural language descriptions. Supports React, Vue, CSS, and Tailwind with real-time design system analysis.
      79,495 npm
      40
      MIT

    • Figma MCP Server by Bao To

      tothienbao6a0
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to extract design systems, analyze components, and maintain design-code consistency from Figma files, providing intelligent component analysis and accessibility compliance.
      81 npm
      29
      MIT

    • DesignPort

      MarlonJD
      F
      license
      B
      quality
      B
      maintenance
      Enables coding agents to read, render, and normalize design documents from Figma and Adobe XD, providing visual context plus structured design data and generating starter code for web, React, Vue, Flutter, SwiftUI, and Jetpack Compose.
      13
      1
      -

    • figma-mcp

      iflow-mcp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to access Figma files and prototypes, allowing them to retrieve design data and assets directly.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: downloading assets, fetching component details, retrieving design tokens, and fetching screen details. No overlap between these operations.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (e.g., download_layer_asset, get_component). Perfectly consistent naming.

    Tool Count5/5

    4 tools is appropriate for a design-focused server covering the core resources: screens, components, assets, and tokens. Neither too few nor too many.

    Completeness5/5

    The tool set covers the primary read-only operations needed from Zeplin: fetching screens, components, assets, and design tokens. No obvious gaps for a viewing/downloading use case.

    Maintenance

    ActivityInactive
    ResponsivenessSlow

    Resources