# How to integrate Zeplin MCP with Claude Code ```json { "title": "How to integrate Zeplin MCP with Claude Code", "toolkit": "Zeplin", "toolkit_slug": "zeplin", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/zeplin/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/zeplin/framework/claude-code.md", "updated_at": "2026-05-12T10:31:12.652Z" } ``` ## Introduction Manage your Zeplin directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Zeplin with - [OpenAI Agents SDK](https://composio.dev/toolkits/zeplin/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/zeplin/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/zeplin/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/zeplin/framework/codex) - [OpenClaw](https://composio.dev/toolkits/zeplin/framework/openclaw) - [Hermes](https://composio.dev/toolkits/zeplin/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/zeplin/framework/cli) - [Google ADK](https://composio.dev/toolkits/zeplin/framework/google-adk) - [LangChain](https://composio.dev/toolkits/zeplin/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/zeplin/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/zeplin/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/zeplin/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/zeplin/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Zeplin to Claude Code ### Connecting Zeplin to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## What is the Zeplin MCP server, and what's possible with it? The Zeplin MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Zeplin account. It provides structured and secure access to your Zeplin workspace, so your agent can perform actions like listing projects, fetching screens, exporting assets, managing components, and collaborating with your design team on your behalf. - Project and styleguide management: Let your agent list, fetch, or organize your Zeplin projects and associated styleguides for faster design handoff and reference. - Screen and asset retrieval: Automatically pull screen details, preview images, or export assets from any project directly into your workflow, no copy-paste required. - Component library access: Have your agent fetch, list, or update components from your shared libraries to keep your design system in sync. - Commenting and collaboration: Enable your agent to read, create, or manage comments on screens or components, streamlining feedback and design review cycles. - Resource linking and metadata extraction: Allow your agent to extract, organize, or provide direct links to design resources and metadata, making documentation and developer handoff seamless. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `ZEPLIN_AUTH_O_AUTH_AUTHORIZE` | Start OAuth authorization (PKCE) | Tool to start OAuth 2.0 authorization code flow for Zeplin apps. Use when initiating user authorization; call before exchanging the code. | | `ZEPLIN_CONNECTED_COMPONENTS_PROJECT_LIST` | List Project Connected Components | Tool to list connected components in a Zeplin project. Use when you have the project_id and need to retrieve connected components in a specific project. | | `ZEPLIN_PROJECT_COLORS_LIST` | List Project Colors | Tool to list colors in a Zeplin project. Use when you need to fetch defined color tokens at the project level after obtaining the project ID. | | `ZEPLIN_PROJECT_COLOR_UPDATE` | Update Project Color | Tool to update a color in a Zeplin project. Use when you need to modify RGBA channels or source ID of an existing color after confirming the project and color IDs. | | `ZEPLIN_PROJECTS_GET` | Get Zeplin Project by ID | Tool to get a Zeplin project by ID. Use when you need detailed info about a specific project after confirming its project_id. | | `ZEPLIN_PROJECTS_MEMBERS_INVITE` | Invite Project Member | Tool to invite a user to a Zeplin project. Use when you need to add a member by email or username to a project after obtaining the project ID. | | `ZEPLIN_PROJECT_TEXT_STYLES_LIST` | List Project Text Styles | Tool to list text styles in a Zeplin project. Use when you need to fetch typography tokens defined at the project level after obtaining the project ID. | | `ZEPLIN_PROJECT_TEXT_STYLE_UPDATE` | Update Project Text Style | Tool to update a text style in a Zeplin project. Use when you need to modify typography settings of an existing text style after confirming the project and text style IDs. | | `ZEPLIN_SCREEN_ANNOTATION_DELETE` | Delete Screen Annotation | Tool to delete a screen annotation in Zeplin. Use when you need to remove a specific annotation from a Zeplin screen given its IDs. | | `ZEPLIN_SCREEN_ANNOTATION_GET` | Get Screen Annotation | Tool to fetch a single screen annotation. Use when you know the screen_id and annotation_id and need the detailed annotation data. | | `ZEPLIN_SCREEN_ANNOTATIONS_LIST` | List Screen Annotations | Tool to list annotations for a Zeplin screen. Use when you have the screen_id and need its annotations. | | `ZEPLIN_SCREEN_ANNOTATIONS_UPDATE` | Update Screen Annotation | Tool to update a screen annotation's content, position, or type. Use after confirming screen_id and annotation_id. | | `ZEPLIN_SCREEN_COMPONENTS_LIST` | List Screen Components | Tool to list components in a Zeplin screen. Use when you have the screen_id and need to retrieve UI components in a specific screen. | | `ZEPLIN_SCREEN_SECTION_GET` | Get Screen Section | Tool to get a single screen section. Use when you need to fetch detailed information of a screen section by its ID after confirming the project and section IDs. | | `ZEPLIN_SCREEN_SECTIONS_LIST` | List Screen Sections | Tool to list screen sections in a Zeplin project. Use when you need a paginated list of screen sections after confirming the project ID. | | `ZEPLIN_SCREEN_VERSION_GET` | Get Screen Version | Tool to retrieve a specific screen version. Use after specifying both screen_id and version_id when you need detailed snapshot metadata. | | `ZEPLIN_SCREEN_VERSIONS_CREATE` | Create Screen Version | Tool to create a new version of a screen. Use when uploading a new design snapshot (PNG or JPEG image) as a screen version. Requires a valid project_id, screen_id, and an image file. Optionally include a commit_message. | | `ZEPLIN_SCREEN_VERSIONS_LIST` | List Screen Versions | Tool to list all versions of a screen. Use when you need to enumerate past screen snapshots after obtaining a screen ID. | | `ZEPLIN_STYLEGUIDE_COLOR_CREATE` | Create Styleguide Color | Tool to create a new styleguide color. Use after obtaining the styleguide ID to define custom color tokens. | | `ZEPLIN_STYLEGUIDE_COLORS_LIST` | List Styleguide Colors | Tool to list colors in a Zeplin styleguide. Use when you need to fetch defined color tokens after obtaining the styleguide ID. | | `ZEPLIN_STYLEGUIDE_COLOR_UPDATE` | Update Styleguide Color | Tool to update a color in a Zeplin styleguide. Use after obtaining the styleguide and color IDs. | | `ZEPLIN_STYLEGUIDE_TEXT_STYLES_LIST` | List Styleguide Text Styles | Tool to list text styles in a Zeplin styleguide. Use when you need to fetch defined typography tokens after obtaining the styleguide ID. | | `ZEPLIN_STYLEGUIDE_TEXT_STYLE_UPDATE` | Update Styleguide Text Style | Tool to update a text style in a Zeplin styleguide. Use when you need to modify typography settings of an existing text style after confirming the styleguide and text style IDs. | | `ZEPLIN_USERS_GET_PERSONAL_PROJECTS` | List Personal Projects | Tool to list personal projects. Use when you need to fetch all projects in the current user's personal workspace after authentication. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Zeplin MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Zeplin account. It provides structured and secure access so Claude can perform Zeplin operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Zeplin account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["zeplin"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http zeplin-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['zeplin'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http zeplin-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Zeplin MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (zeplin-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http zeplin-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Zeplin MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your zeplin-composio entry in the list - This confirms that Claude Code can now access Zeplin tools If everything is wired up, you should see your zeplin-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Zeplin The first time you try to use Zeplin tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Zeplin - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Zeplin authorization flow - Return to the terminal and start using Zeplin through Claude Code Once authenticated, you can ask Claude Code to perform Zeplin operations in natural language. For example: - "List all project styleguides in Zeplin" - "Get all screens for a specific project" - "Fetch comments from a specific Zeplin screen" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["zeplin"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http zeplin-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['zeplin'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http zeplin-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Zeplin with Claude Code using Composio's MCP server. Now you can interact with Zeplin directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Zeplin operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Zeplin operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Zeplin MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/zeplin/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/zeplin/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/zeplin/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/zeplin/framework/codex) - [OpenClaw](https://composio.dev/toolkits/zeplin/framework/openclaw) - [Hermes](https://composio.dev/toolkits/zeplin/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/zeplin/framework/cli) - [Google ADK](https://composio.dev/toolkits/zeplin/framework/google-adk) - [LangChain](https://composio.dev/toolkits/zeplin/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/zeplin/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/zeplin/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/zeplin/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/zeplin/framework/crew-ai) ## Related Toolkits - [Figma](https://composio.dev/toolkits/figma) - Figma is a collaborative interface design tool for teams and individuals. It streamlines design workflows with real-time collaboration and easy sharing. - [Abyssale](https://composio.dev/toolkits/abyssale) - Abyssale is a creative automation platform for generating images, videos, GIFs, PDFs, and HTML5 content programmatically. It streamlines and scales visual content production for marketing, design, and operations teams. - [Alttext ai](https://composio.dev/toolkits/alttext_ai) - AltText.ai is a service that generates alt text for images automatically. It helps boost accessibility and SEO for your visual content. - [Bannerbear](https://composio.dev/toolkits/bannerbear) - Bannerbear is an API-driven platform for generating images and videos automatically at scale. It helps businesses create custom graphics, social visuals, and marketing assets using powerful templates. - [Canva](https://composio.dev/toolkits/canva) - Canva is a drag-and-drop design suite for creating professional graphics, presentations, and marketing materials. It makes it easy for anyone to design with beautiful templates and a vast library of elements. - [Claid ai](https://composio.dev/toolkits/claid_ai) - Claid.ai delivers AI-driven image editing APIs for tasks like background removal, upscaling, and color correction. It helps automate and enhance image workflows with powerful, developer-friendly tools. - [Cloudinary](https://composio.dev/toolkits/cloudinary) - Cloudinary is a cloud-based platform for managing, uploading, and transforming images and videos. It streamlines media workflows and delivers optimized assets globally. - [Cults](https://composio.dev/toolkits/cults) - Cults is a digital marketplace for 3D printing models, connecting designers and makers. It lets creators share, sell, and discover a huge variety of printable designs easily. - [DeepImage](https://composio.dev/toolkits/deepimage) - DeepImage is an AI-powered image enhancer and upscaler. Get higher-quality images with just a few clicks. - [Dreamstudio](https://composio.dev/toolkits/dreamstudio) - DreamStudio is Stability AI’s platform for generating and editing images with AI. It lets you easily turn ideas into stunning visuals, fast. - [Dynapictures](https://composio.dev/toolkits/dynapictures) - Dynapictures is a cloud-based platform for generating personalized images at scale. Instantly create hundreds of custom visuals using your data sources, like Google Sheets. - [Fal.ai](https://composio.dev/toolkits/fal_ai) - Fal.ai is a generative media platform offering 600+ AI models for images, video, voice, and audio. Developers use Fal.ai for fast, scalable access to cutting-edge generative AI tools. - [Gamma](https://composio.dev/toolkits/gamma) - Gamma is an AI-powered platform for making beautiful, interactive presentations and documents. It lets anyone create and share engaging decks with minimal effort. - [Html to image](https://composio.dev/toolkits/html_to_image) - Html to image converts HTML and CSS into images or captures web page screenshots. Instantly generate visuals from code or web content—no manual screenshots needed. - [Imagior](https://composio.dev/toolkits/imagior) - Imagior is an AI-powered image generation platform that lets you create and customize images using dynamic templates and APIs. Perfect for businesses and creators needing fast, scalable visuals without design hassle. - [Imejis io](https://composio.dev/toolkits/imejis_io) - Imejis io is an API-based image generation platform with powerful customization and template support. It lets you create and modify images in seconds, no manual design work required. - [Imgix](https://composio.dev/toolkits/imgix) - Imgix is a real-time image processing and delivery service for developers. It helps you optimize, transform, and deliver images efficiently at any scale. - [Kraken io](https://composio.dev/toolkits/kraken_io) - Kraken.io is an image optimization and compression platform. It helps you shrink image file sizes while keeping visual quality intact. - [Logo dev](https://composio.dev/toolkits/logo_dev) - Logo.dev is an API and database for high-resolution company logos and brand metadata. Instantly fetch official logos from any domain without scraping or manual searching. - [Miro](https://composio.dev/toolkits/miro) - Miro is a collaborative online whiteboard platform for teams to brainstorm, design, and manage projects visually. It streamlines teamwork by enabling real-time idea sharing, diagramming, and workflow planning in a single space. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Zeplin MCP? With a standalone Zeplin MCP server, the agents and LLMs can only access a fixed set of Zeplin tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Zeplin and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Code? Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Zeplin tools. ### Can I manage the permissions and scopes for Zeplin while using Tool Router? Yes, absolutely. You can configure which Zeplin scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Zeplin data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)