Figma To Code MCP

Why This Project?

Figma To Code MCP specializes in extracting only the information LLMs need to build UIs while removing Figma-specific metadata that isn't relevant for code generation. The result:

• ✅ 99.5% size reduction on real Figma files (65 MB → 128 KB)

• ✅ Compact, CSS-mappable fields (style.background, layout.direction, style.fontSize)

• ✅ Complete UI-building data preserved (layout, styling, text, components)

• ✅ Node-local layout and styles with reusable values in a shared token registry

• ✅ Omits Figma internals - no bounding boxes or constraint metadata

• ✅ Variable resolution - resolves Figma variables to actual values

• ✅ SVG support - exports vector graphics to disk

• ✅ Pattern collapsing - deduplicates repeating UI patterns

Give Cursor and other AI-powered coding tools access to your Figma files with this Model Context Protocol server.

Related MCP server: Framelink Figma MCP Server

Available Tools

get_figma_design exports SVG assets automatically. Its response contains svgAssetsFolder and relative svgPathInAssetFolder filenames; combine them to locate each file. Use svgOutputDir to export directly to a chosen assets directory. It also renders the requested node as a 1x PNG: its response contains renderedDesignNodeAssetsFolder and the file name renderedDesignNodePathInAssetFolder, which you can use to compare the built result with the design. There is no separate registered read_vector_svg tool.

By default get_figma_design returns the components the design uses in componentSets, each with propKeys and propValues (the values each prop takes across the set's members). Every set is written to its own file in componentSetsFolder, as YAML or JSON to match the output format, and componentSets lists each set's file, propKeys and propValues. A set larger than 228 KB becomes a folder named after the set: its file is <set>/index.yaml (index.json in JSON output), which lists the variants, and each variant is its own <nodeId>.yaml beside it, with : replaced by - (for example 7-770.yaml). These examples assume the default YAML output; with JSON output every file ends in .json. A COMPONENT_SET root gets the same treatment: when its variants exceed 228 KB, its children move out, root.file points at <name>/index.yaml, and each variant is a <variant name>.yaml beside it, since root variants carry no node id. Every file value is relative to componentSetsFolder, so a variant's file is <set>/<nodeId>.yaml, not relative to its set folder. A large SECTION root keeps each frame as a stub in root.children, and each frame's design is in its file in framesFolder (see Resolving frame files). For building components from a component library, pass includeComponentVariants: true to also get every other variant of those components (all sizes, colors, and states), with their props and any visuals that can be fetched. That fetches more from Figma and returns a larger response.

With --skip-image-downloads, only get_figma_design is registered; SVG export remains available, and no node PNG is rendered.

Required Scopes

Create a Figma personal access token with these scopes:

Note: Variable resolution requires Enterprise plan. Set resolveVariables: false if not on Enterprise.

If comment access is unavailable, extraction continues without comments and logs a warning.

How it works

1. Open your IDE's chat (e.g. agent mode in Cursor).

2. Paste a link to a Figma file, frame, or group.

3. Ask Cursor to implement the design.

4. Cursor fetches CSS-aligned, LLM-optimized design data and generates accurate code.

Agents that build a page from a design should follow For LLMs.

This MCP server transforms Figma API data into an LLM-friendly format:

• Compact layout/style fields (layout.direction, style.background, style.fontSize) instead of verbose Figma internals

• Node-local styles with every distinct design value referenced from the tokens registry

• Flexbox primitives for auto-layout, with parent-local positioning for overlays and freeform graphics

• Complete UI data (colors, typography, spacing, effects)

• 99.5% size reduction while preserving all UI-critical information

The current response uses schema v3. V3_CSS_PROPERTY_MAPPING.md describes the older v2 mapping, not the current response contract.

Interpreting visual details in v3

The response includes optional fields for details that cannot be represented by one text style or a simple flex layout:

The existing full text field and node-level style remain present. When textRuns exists, render its runs in order rather than rendering text a second time. Resolve the node's base typography token first, then apply each run's scalar overrides. Run text concatenates to the original full text; plain runs inherit the base style. Explicit normal, none, and zero values reset inherited styling.

For positioned children, keep the emitted containing block, local dimensions, and offsets. Real auto-layout siblings stay in flex flow; overlay notifications, chart curves, and guides can share an absolute coordinate space. A Figma layout mode of NONE is not converted into a flex column.

borderWidths replaces the uniform borderWidth for asymmetric strokes. Apply the shared border color only to the indicated edges; do not invent a surrounding box border. Uniform borders continue using borderWidth.

Gradient handles may lie outside the unit square; do not clamp them or discard them in favor of a default direction.

SVG exports keep original node-local coordinates and include the union of the local canvas and visible geometry. Each exported node's svgViewport matches the file's viewBox. Keep the node's original layout footprint as a wrapper, then place the SVG or image at svgViewport.x / y (a missing one means 0), with the viewport's width / height. Do not stretch this expanded asset to the original node dimensions: chart series can have different ink bounds but must share the same local coordinate system. Preserve ancestor clipping. Solid paint colors are baked into design-exported assets so external images retain their colors too.

For LLMs

Follow this section when you build a page or component from a Figma node with get_figma_design.

Response overview

Responses are large. Full pages in testing were 200–360 KB, so read root in parts rather than all at once.

The reference picture

renderedDesignNodePathInAssetFolder is a 1x PNG of the requested node. It shows the design as Figma renders it, and it is the reference for both building and checking.

• Open the PNG before you write code. For a component set it shows every variant in a grid; for a frame it shows the frame.

• Use it to split the page into sections, then match each section to a part of root.children.

• Render your build at the same width and compare it with the PNG section by section. Keep fixing until the differences are gone or you can explain them.

• For a frame, the PNG's pixel width equals the frame's layout width (for example 410 px for a 410 px frame).

• The PNG is missing when the server runs with --skip-image-downloads, when Figma returns no image, or when the download fails. Without it, say that the visual check was skipped instead of guessing.

Process: from design to page

1. Fetch one node per breakpoint. A frame named like Startseite (XS) is one breakpoint. Fetch each breakpoint you need separately.

2. Use a fresh export folder per design. Pass svgOutputDir. The folder receives the SVGs, the PNG and component-sets/. Files from earlier runs stay there, so don't reuse a folder for a different design.

3. Read the reference picture and list the page's sections.

4. Plan components. Make one component per repeated section or per component name. Use componentSets[name].propValues to see each component's variant options.

5. Map tokens once. Create one theme file that maps each token key the page uses to a CSS variable or theme value. Don't copy hex values into each element.

6. Build section by section. Map layout to flex: direction, gap, padding, width, height, grow, align and justify. Use absolute positioning only where layout.position is absolute, with left and top relative to the parent.

7. Render text from text. When textRuns exists, render its runs in order over the base typography token and don't render text again (see Interpreting visual details).

8. Place vectors by viewport. For each vector, load the file named by svgPathInAssetFolder from svgAssetsFolder. Position it at svgViewport.x and y (a missing value means 0) and size it to svgViewport.width and height. Don't stretch it to the node size.

9. Handle image fills. If a node uses an image fill, such as a photo or screenshot, call get_image_fills to get its download URL.

10. Verify the build against the reference picture, as described above.

11. Ask when the target stack, the breakpoints or the expected output are unclear, instead of guessing.

Resolving component files

• root.file, componentSets[name].file and the file entries in an index file are relative to componentSetsFolder. Join them to that folder instead of guessing a location.

• Names become file names by replacing each run of characters other than A–Z, a–z, 0–9 and _ with one -. For example, Variant=Start 1, Color=Default becomes Variant-Start-1-Color-Default.json, and node 7:770 becomes 7-770.json. These examples use JSON output; with the default YAML output the extension is .yaml.

• Use the key from componentSets as written. Keys can include a library reference in brackets, such as headline-combo [zd1Yd…/3574:6]. Read the file value rather than building the path from the key.

Resolving frame files

• A SECTION root whose frame children together exceed 228 KB keeps each frame as a stub in root.children, with its name, its type and a file. The full frames are written to framesFolder.

• file is relative to framesFolder. Join them to read a frame. The frame file holds the full frame node and only the tokens it uses.

• Frame file names follow the naming rule above, with the output extension. Frames that share a name get -2, -3 and so on, such as Cronjobs-2.yaml.

• A section whose frames stay under 228 KB, or that holds anything other than frames, stays inline with no framesFolder.

Pitfalls

• Root node … not found: the node ID is wrong or the file can't be read. Convert the URL's node-id=519-8870 to 519:8870, and check that the node exists in that file.

• Repeated calls: the server caches a design for 5 minutes for the same inputs. Keep the first response instead of fetching again. Changing includeComponentVariants, resolveVariables or the credentials fetches again.

• interactions describe prototype hover and click targets. Ignore them unless the build needs that behavior.

Getting Started

Many code editors and other AI clients use a configuration file to manage MCP servers.

This server requires Node.js 18 or later.

The tmegit-figma-to-code-mcp server can be configured by adding the following to your configuration file.

MacOS / Linux

{
  "mcpServers": {
    "Figma To Code MCP": {
      "command": "npx",
      "args": ["-y", "@tmegit/figma-to-code-mcp", "--figma-api-key=YOUR-KEY", "--stdio"]
    }
  }
}

Windows

{
  "mcpServers": {
    "Figma To Code MCP": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@tmegit/figma-to-code-mcp",
        "--figma-api-key=YOUR-KEY",
        "--stdio"
      ]
    }
  }
}

Or you can set FIGMA_API_KEY and PORT in the env field.

HTTP mode

Omit --stdio to serve Streamable HTTP at /mcp and legacy SSE at /sse with messages posted to /messages. Concurrent clients have independent MCP sessions; closing one does not close the others. Library-variable prefetch is shared across sessions using the same configured credentials.

For embedded use, startHttpServer(host, port, server) still accepts a server returned by this package's createServer. For a custom McpServer, pass a per-session factory as the third argument to support concurrent clients; a single external instance remains single-session.

createServerFactory(auth, options) prepares shared configuration once. If you add custom tools, register them on every server returned by your factory: registrations added to a single supplied instance are not copied to its generated siblings. Custom asynchronous factories must settle so shutdown can finish cleaning up pending connections.

The default host is 127.0.0.1. These endpoints do not add client authentication; do not expose them to an untrusted network without an authenticated proxy.

Configuration

The server reads configuration from CLI flags and environment variables. If both are set, the CLI flag wins.

Notes:

• --library-file-keys and FIGMA_LIBRARY_VARIABLE_PREFETCH_FILE_KEYS are comma-separated Figma library file keys.

• FIGMA_MCP_CACHE_PATH may point to either a JSON file or a directory. The server adds a credential fingerprint before .json to isolate cached library variables, for example figma-mcp-library-cache.<fingerprint>.json inside a directory. Existing unscoped cache files are not reused by server startup.

• The library cache is used only when library file keys are configured.

• FIGMA_MCP_REFRESH_CACHE forces a re-fetch on startup even if a cache file exists.

Example .env:

FIGMA_API_KEY=your_figma_pat
# prefetch variables (tokens etc) from specific library files on startup to avoid T2 calls during design fetch
FIGMA_LIBRARY_VARIABLE_PREFETCH_FILE_KEYS=abc123,def456
FIGMA_MCP_CACHE_PATH=./cache
FIGMA_MCP_CACHE_TTL_MS=604800000
# Uncomment to force cache refresh on next startup
# FIGMA_MCP_REFRESH_CACHE=1

API Calls & Rate Limits

On a design-cache miss, get_figma_design can make these API calls:

Request counts vary with the number of unique component keys, libraries, node batches, and retries. Components from multiple libraries are supported; unavailable library metadata falls back to usable instance data.

Requests are paced per Figma tier so no tier exceeds its per-minute budget (10, 25, and 50 requests for tiers 1, 2, and 3 on Professional Dev/Full seats). If Figma still answers with a 429, only that tier pauses for the Retry-After time, and the request is retried up to three times. A GET that fails at the network level is retried once through curl, which helps behind corporate proxies. The retry runs in the same request slot, so it still counts once against the tier budget.

Compatible design-cache hits avoid these Figma calls but still export assets, including the node PNG, into the requested directory. The PNG is downloaded from Figma's image URL, which is not a Figma API call. Changing credentials or result-affecting options does not reuse an incompatible design response.

Effective styles are read from node properties, including node-specific overrides. The tool does not make a separate /styles request. The library's existing fetchStyles export and styleMap parameter remain available for compatibility; shared-style names are not currently emitted in the design response.

For Professional plan with Dev/Full seat: 10 req/min (Tier 1), 25 req/min (Tier 2), 50 req/min (Tier 3).

Star History

Acknowledgment

This project was initially inspired by the ideas explored in the original Figma Context MCP by GLips: https://github.com/glips/figma-context-mcp

While the original project provides a Model Context Protocol (MCP) server that simplifies Figma data for use with AI coding agents, this implementation has been substantially redesigned with a different data model, API, and processing approach, and should be considered an independent system.