# Figma

Official Figma MCP server and skills for design-to-code workflows. Read design context from Figma files, implement designs, use Code Connect, write to the canvas, and generate Figma designs from web pages.

Figma is a browser-based collaborative interface design tool. This integration allows access to and processing of Figma design files and resources.

- Category: Design
- Connection: Sign in. Sign in with your Figma account, or paste an API key instead.
- Plans: Free: Not included; MCP only ($9/mo): 2,000 calls a month; Pro: 20,000 calls a month; Max: 20,000 calls a month
- Vendor site: https://figma.com

## Tools

- Get comments (`FIGMA__GET_COMMENTS`): Retrieves all comments from a Figma file, including their content and author information.
- Get component (`FIGMA__GET_COMPONENT`): Retrieves a specific component node from a Figma file based on the given file key and node ID. Returns detailed information about the component, including its properties and metadata.
- Get file (`FIGMA__GET_FILE`): Retrieves the document structure of a Figma file based on the given file key. Returns the entire document as JSON including nodes, their names, and types.
- Get file component sets (`FIGMA__GET_FILE_COMPONENT_SETS`): Returns a list of component sets in a file, indicating which components belong to which component set.
- Get file nodes (`FIGMA__GET_FILE_NODES`): Retrieves the nodes present in a Figma file based on the given file key and node IDs.
- Get file versions (`FIGMA__GET_FILE_VERSIONS`): Retrieves the version history of a Figma file based on the given file key.
- Get image (`FIGMA__GET_IMAGE`): Retrieves images rendered from a Figma file based on the given file key and node IDs.
- Get image fills (`FIGMA__GET_IMAGE_FILLS`): Returns download links for all images present in image fills in a document.
- Get project files (`FIGMA__GET_PROJECT_FILES`): Lists the files in a given project based on the project ID.
- Get style (`FIGMA__GET_STYLE`): Retrieves a specific style node from a Figma file based on the given file key and node ID. Returns detailed information about the style, including its properties and metadata.
- Get team projects (`FIGMA__GET_TEAM_PROJECTS`): Retrieves a list of projects within a team based on the given team ID.

## Skills included

- figma-code-connect: Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.
- figma-code-workflows: Import or upload local HTML or project files into Figma, choose editable Design frames, runnable Code Layers or standalone Code (also known as Make), and repair imported previews. Use only when the user explicitly names editable Design layers, a runnable Code Layer, or a standalone Code/Make file, or supplies a Figma file key/link as the import destination. Generic code or code-component requests need output clarification before using this workflow.
- figma-create-new-file: Always use this skill when the user wants to create a new Figma Design, FigJam, or Slides file. You MUST invoke this skill BEFORE every `create_new_file` tool call.
- figma-design-to-code: **MANDATORY prerequisite** — you MUST invoke this skill BEFORE calling the `get_design_context` Figma MCP tool. You MUST trigger this skill whenever the user wants to implement, build, port, or code up a Figma design as code. Example prompts (not exhaustive) are 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'design to code'. This skill provides critical instructions and steps to the agent on how to correctly implement Figma designs in code and must NOT be skipped.
- figma-generate-design: Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma.
- figma-generate-diagram: MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
- figma-generate-library: Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. Also use when the user asks to create or generate any component in Figma — even a single one — since components require proper variable foundations, variant states, and design token bindings to be production-quality. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.
- figma-generative-plugins: **MANDATORY prerequisite** — load this skill before calling `create_generative_plugin` or `update_generative_plugin`. Use when the user asks to create, author, change, fix, or extend a reusable generative Figma plugin.
- figma-implement-motion: Translates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when `get_design_context` returns motion data or instructs you to call `get_motion_context`.
- figma-shaders: **MANDATORY prerequisite** — load this skill before calling `create_shader` or `update_shader`. Use when the user asks to create, author, change, fix, or iterate on a shader effect, shader fill, custom effect, custom fill, or procedural shader in Figma.
- figma-spec: This skill is required to create, read, edit, review, or comment on Figma specs. You must read it when working on a PRD, brief, RFC or any kind of document in either a standalone Figma spec or a Figma spec embedded in a Figma Design or Figjam file.
- figma-swiftui: SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.
- figma-use: **MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
- figma-use-figjam: This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
- figma-use-motion: Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node. Also covers working with custom animation styles.
- figma-use-slides: This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.

## Questions

### How do I connect Figma to Krypton?

Open Integrations in Krypton, find Figma and choose Sign in. Every bot in the workspace can then use it, and you choose which bots get which apps.

### Which plan includes Figma?

MCP only with 2,000 calls a month, Pro and Max with 20,000. Calls are shared by every catalog app in the workspace. Past the monthly number they keep working from AI credits at $0.90 per 1,000 calls; the count resets on the 1st (UTC) and a retried call counts once.

### Can I use Figma from Claude or Cursor?

Yes. Connect it in your workspace, then add https://mcp.krypton.bot as a streamable HTTP MCP server with your kmcp_ workspace key. Calls count toward the same monthly number.

Back to the [MCP catalog](https://krypton.bot/mcp-catalog/).
