Pod to App: Claude Code
How to install the Figma MCP server in Claude Code
By Sophie Filer · Updated 10 Nov 2026 · Steps checked against Figma's own docs on 10 Nov 2026
The short answer
Run claude plugin install figma@claude-plugins-official in your terminal, then sign in to Figma when Claude Code asks. That adds Figma's hosted server and its skills in one go; after that, paste a link to a frame and ask Claude Code to build it.
claude plugin install figma@claude-plugins-official- Install
- Plugin, or one claude mcp add
- Sign-in
- Figma account in the browser
- Runs on
- Figma's hosted server
- Limits
- 6 calls a month on Starter
Before you start
- Claude Code installed and signed in.
- A Figma account. Any plan can connect, but how much you can use it depends on your seat, as the limits section below explains.
- A design file you can open, and a project folder where the code should go.
Install it step by step
- Step 1: In your normal terminal, run the plugin command at the top of this page. The plugin brings the server settings plus ready-made skills for common Figma jobs.
- Step 2: Start Claude Code in your project folder and type
/mcp. Pick figma and choose to authenticate. - Step 3: Your browser opens a Figma page. Click Allow access, then go back to the terminal.
- Step 4: Check it with
claude mcp list: figma should show as connected. - Step 5: In Figma, right-click a frame or layer and choose Copy link to selection. Paste that link into Claude Code and ask: "Build this as a component in our app."
Prefer no plugin? Add the server by hand
The plugin is what Figma recommends, but the bare server works on its own. This adds only the connection, without the bundled skills:
claude mcp add --transport http figma https://mcp.figma.com/mcpThen sign in through /mcp as above. Add --scope user before the name to have Figma in every project, not just this folder. claude mcp get figma shows what was saved, and claude mcp remove figma takes it out again.
What a Figma link gives Claude Code
Claude Code does not open the link in a browser. It reads the node ID from the URL and asks Figma's server about that one frame. Four tools do most of the work:
| Tool | What Claude Code gets |
|---|---|
get_design_context | Code for the frame, React with Tailwind unless you ask for something else, such as plain HTML or SwiftUI |
get_variable_defs | The colours, spacing and type variables the frame uses |
get_screenshot | A picture of the frame, so it can compare its result |
get_metadata | A light outline of layer names, sizes and positions, for selections too big to fetch in full |
Teach it your codebase with CLAUDE.md
The generated code is a starting point, not your house style. Figma suggests adding rules to CLAUDE.md so Claude Code maps the design onto what you already have. Rules worth writing down:
- Fetch the design context first, then a screenshot, and only then start writing code.
- Swap Tailwind classes for your own design tokens where you have them.
- Reuse existing buttons, inputs and icons instead of making new ones.
- When Figma hands back a localhost link for an image or SVG, use it as is, and do not add a new icon package.
How many calls your Figma seat allows
| Your Figma seat | What you get |
|---|---|
| Starter plan, or a View or Collab seat on any plan | Up to 6 tool calls a month, enough to try it and little more |
| Dev or Full seat on Professional, Organization or Enterprise | Per-minute limits, the same as Tier 1 of the Figma REST API |
Tools that write to the canvas are not counted against these limits. Writing back to Figma works only with the hosted server and is free while it is in beta.
If it does not work
| What you see | What to do |
|---|---|
| figma is listed but needs authentication | Run /mcp inside Claude Code, pick figma and sign in again. |
| Rate limit errors after a few tries | You are on a View, Collab or Starter seat. Ask for a Dev or Full seat, or save your calls for the frames that matter. |
| Claude Code says it cannot find the design | Copy the link with Copy link to selection, so it carries a node-id. A plain file link has no frame in it. |
| Reply is cut short or vague | The selection is too big. Ask for get_metadata first, then fetch smaller parts one by one. |
MCP Shelf take
Is Figma worth adding to Claude Code?
This is the most useful way we know to get from a Figma frame to working code in Claude Code, because the agent sees real layer data and variables, not a screenshot it has to guess from. Two things decide whether it pays off. First, your seat: on Starter or a View seat, six calls a month runs out in one afternoon. Second, your rules: without a CLAUDE.md that names your components and tokens, you get tidy React and Tailwind that you then rewrite. Get both right and it saves real hours on every new screen.
Sophie Filer
Questions
Is the Figma MCP server free in Claude Code?
Connecting is free on every plan, but Starter plans and View or Collab seats get only 6 tool calls a month. Dev and Full seats on paid plans get per-minute limits instead, which is what everyday use needs.
Do I need the Figma desktop app for Claude Code?
No. The hosted server at mcp.figma.com works from links alone. Figma also has a desktop server you turn on in Dev Mode, which reads your current selection, but it needs a Dev or Full seat and cannot write to the canvas.
Can Claude Code make code in something other than React?
Yes. React with Tailwind is only the default. Say which framework you want, for example Vue, plain HTML and CSS, or SwiftUI, and add it to CLAUDE.md so you do not have to repeat it.
What is the difference between the Figma plugin and claude mcp add?
Both connect the same hosted server. The plugin also installs skills that guide Claude Code through common Figma jobs, so it is the better first choice; the bare command is handy when you only want the tools.
Sources: the steps on this page are written in our own words from Figma MCP Server (official)'s own install docs, the README. If they disagree with this page, the project's docs win; please tell us from the server page.
