Skip to main content
Guide7 min read·Updated June 10, 2026
🧩

How to Install the Figma MCP in Claude Code (2026)

B

A. Frans

Published June 10, 2026

MCPFigmaClaude CodeDesign to CodeTutorial

Pasting a Figma screenshot into Claude Code and asking it to "build this" gets you something that looks roughly right and gets every spacing value wrong. The Figma MCP fixes that. Instead of guessing from a picture, Claude Code reads the actual design: the exact padding, the color variables, the component names, the auto-layout rules. From that it writes code that matches what your designer actually built.

This guide walks through both ways to connect Figma to Claude Code: Figma's official Dev Mode MCP server, and the free community option called Framelink. You'll have one of them running in about ten minutes.

What the Figma MCP actually does

MCP (Model Context Protocol) is the standard that lets Claude Code talk to outside tools. A Figma MCP server exposes your designs to Claude as structured data rather than an image. When you select a frame and ask Claude to implement it, the agent can pull the real layout tree, design tokens, and variable names, so the generated component uses your spacing-md token instead of a hardcoded 16px it eyeballed.

There are two servers worth knowing:

Official Dev Mode MCPFramelink (community)
Made byFigmaOpen source (GLips)
How it connectsLocal server in Figma desktop appPersonal access token + npx
Plan neededDev or Full seat (paid plans)Any plan, including free
CostIncluded with eligible seatFree
GitHubfigma.com docsgithub.com/GLips/Figma-Context-MCP
If your team already pays for Figma with Dev seats, use the official one. If you're on a free Figma account or want zero extra licensing, Framelink is the answer.

Prerequisites

Before either method, make sure you have:

  • Claude Code installed and working (claude --version returns a version)
  • A Figma account with a file you want to convert
  • For the official server: the Figma desktop app (the browser version can't run the local server) and a Dev or Full seat
  • For Framelink: Node.js installed (node --version returns v18 or higher)

Method 1: Figma's official Dev Mode MCP server

This server runs locally inside the Figma desktop app and exposes the file you're working in.

Step 1: Update the Figma desktop app. The MCP server only exists in recent builds. Open Figma desktop, check for updates, and restart it.

Step 2: Enable the server. In the Figma desktop app, open the main menu and go to Preferences. Look for the option to enable the local MCP server (in current builds it's under Preferences → "Enable local MCP server" / Dev Mode settings). Turn it on. Figma will confirm the server is running locally, typically at http://127.0.0.1:3845.

Step 3: Add it to Claude Code. From your terminal, register the server:

claude mcp add --transport sse figma-dev-mode http://127.0.0.1:3845/sse

Figma has been moving this endpoint toward a streamable HTTP path (/mcp). If the SSE URL doesn't connect, check the current endpoint shown in Figma's MCP settings panel and swap it in.

Step 4: Verify the connection. Start Claude Code in your project and run:

/mcp

You should see figma-dev-mode listed as connected. If it's not, confirm the Figma desktop app is open and the server toggle is still on. The server only runs while the app is open.

Step 5: Use it. In Figma, select the frame or component you want. Then in Claude Code, ask something like: "Implement the selected Figma frame as a React component using our existing Button." Claude pulls the real design data and generates the code against it.

Framelink uses a Figma personal access token instead of the desktop app, so it works on free accounts and headless setups.

Step 1: Create a personal access token. In Figma (web or desktop), go to Settings → Security → Personal access tokens. Generate a new token and give it read access to file content. Copy it immediately, because Figma shows it only once.

Step 2: Add the server to Claude Code. Register Framelink, passing your token:

claude mcp add figma-context -- npx -y figma-developer-mcp --figma-api-key=YOUR_TOKEN --stdio

Replace YOUR_TOKEN with the token from step 1. The npx call pulls the package on first run, so the initial start takes a few seconds.

Step 3: Verify. Run /mcp inside Claude Code and confirm figma-context shows as connected.

Step 4: Use it with a link. Framelink works from Figma URLs. Copy the link to a frame (right-click a frame → Copy link), paste it into Claude Code, and ask it to build that frame. The full setup and options live in the GitHub README at github.com/GLips/Figma-Context-MCP.

A security note on the token

The Framelink method hands an API token to a local process. Two habits keep this safe. First, scope the token to read-only file content. It doesn't need write or admin access to convert designs. Second, don't paste the token into a shared config file that lands in git; keep it in an environment variable or your shell's secret store. The official Dev Mode server avoids the token entirely because it only binds to localhost and only exposes the file you have open, which is part of why teams on paid plans prefer it.

Troubleshooting

/mcp shows the server as failed or disconnected. For the official server, the Figma desktop app must be running with the toggle on. Closing Figma kills the server. For Framelink, check that node and npx are on your PATH and that the token is valid (a revoked token fails silently).

Claude generates code but ignores my variables. Make sure you've selected the actual frame in Figma before asking (official server) or pasted the correct frame URL (Framelink). Pointing at a whole page instead of a component gives Claude too much to chew on.

Port 3845 already in use. Another instance of Figma or a stale process may be holding it. Quit Figma fully and reopen, or restart your machine if the port stays locked.

How to get good output once it's connected

Connecting the server is the easy part. Getting code you'd actually ship takes a few habits.

Select one component, not a whole page. When you point Claude at an entire screen, it has to infer structure across dozens of layers and the result gets muddy. Feed it a single button, card, or form section, get that right, then move up to the next piece. Designs built with proper auto-layout and named components translate far better than a pile of absolutely-positioned rectangles, so the cleaner your Figma file, the cleaner the code.

Tell Claude what to reuse. The MCP gives it your design data, but it doesn't know your codebase unless you say so. A prompt like "build this using our existing Button and the tokens in theme.ts" produces code that fits your project instead of a standalone copy with hardcoded values. This is where the Figma MCP pays off over a screenshot: the agent can map your spacing-md variable to your code's spacing token because it can see both.

Expect to review and iterate. The MCP gets you most of the way, and you finish the last stretch by hand: adjusting responsive behavior, wiring up state, fixing the one nested component it misread. That's normal, and it's still far faster than building from a static image.

Which method to choose

If your team is on a paid Figma plan with Dev seats, the official Dev Mode MCP server is the cleaner path: no tokens, tighter scope, and Figma builds and maintains it. If you're on a free account, working solo, or scripting this on a server without the desktop app, Framelink gets you the same design-to-code workflow at no cost. Both produce far better results than handing Claude a screenshot and hoping.

Once it's running, pair it with a frontend design skill to push the generated components toward production quality instead of stopping at a rough match.

FAQ

Do I need a paid Figma plan to use the MCP?

For the official Dev Mode server, yes. You need a Dev or Full seat. For the Framelink community server, no. It works with a free Figma account using a personal access token, which makes it the better option for solo developers and hobby projects.

Does the Figma desktop app have to stay open?

For the official server, yes. It runs locally inside the desktop app and stops the moment you quit Figma. The Framelink method talks to Figma's web API, so it doesn't need the desktop app open at all.

Can the MCP edit my Figma designs?

The standard read-only setup only lets Claude read your designs to generate code, and it doesn't change your files. Keep your token scoped to read access so it can't, even by accident.

Why is my generated code still not pixel-perfect?

The MCP gives Claude accurate data, but the quality of the output also depends on your prompt and your codebase. Tell Claude which existing components and tokens to reuse, select a single clean component rather than a whole page, and iterate. It gets you 90% there; the last 10% is normal review.

Is this different from pasting a Figma screenshot?

Completely. A screenshot is a flat image Claude has to interpret, so it guesses at spacing, colors, and structure. The MCP exposes the real design tree: exact values, named variables, component hierarchy. The code matches the source instead of approximating it.

Share this article

📬

Get More AI Tool Guides

New comparisons and guides every week. Join thousands of professionals staying ahead of the AI curve.