Figma MCP: What It Is and How to Connect It to Claude Code
What Figma MCP is, the exact command to connect it to Claude Code, remote vs desktop server, the tools and skills it has today, writing to Figma, limits by plan and security.

Figma MCP is Figma's official connection between your design files and an AI agent such as Claude Code. Connect it once and a pasted Figma link gives Claude your real frames, variables and components, not just a screenshot. Since March 2026 it also writes, so Claude can build and edit frames in your file. This guide has the exact setup commands, what the server can do today, the limits by plan and the security checks worth making.
What Figma MCP is
MCP stands for Model Context Protocol, the open standard Anthropic released on 25 November 2024 for connecting AI assistants to the systems where data lives. Figma shipped its server in beta on 4 June 2025 with three tools, for code, images and variables, and it needed the Figma desktop app. Today it has more than 30 tools and two versions, remote and desktop.
The server does not turn a design into finished code. Figma's own FAQ says it hands your agent structured design information, and Claude writes the code, so the result depends on the context, the model and your prompt. Figma calls the server a multiplier when your components, variables and styles already line up with your code, which is design system work. Code Connect, Figma's link from a component to its code file, tells Claude exactly where to look.
A screenshot in chat
Spacing guessed from pixelsColors guessed from a pictureComponents rebuilt from scratch
ā Claude guesses
A Figma link with MCP
Layout and spacing as dataThe variables used in the selectionThe path to your code component, with Code Connect
ā Claude reads
Connect Figma MCP to Claude Code
You need Claude Code (setup guide) and a Figma account. Run this once in your terminal:
claude mcp add --transport http figma https://mcp.figma.com/mcp
Then:
- Start a new Claude Code session.
- Type
/mcpand select figma. - Select Authenticate. A browser page opens.
- Click Allow access, then go back to Claude Code. It says "Authentication successful. Connected to figma".
- Type
/mcpagain to confirm.
Claude Code saves the server for the current project only. To get it in every project, add --scope user after mcp add.
The plugin route. Figma recommends its plugin: run claude plugin install figma@claude-plugins-official, restart Claude Code and type /plugin. Open the Installed tab, select the figma server, press Enter, then Enter again, and click Allow access in the browser. You get the same server plus Figma's skills, which writing to Figma needs.
Adding the server by hand does not install the skills. If the plugin command fails, your organization may block plugins, so use the command above.
To use it, right-click a frame in Figma, choose Copy link to selection and paste the link into your prompt. Claude does not open the link. It takes the node ID, the frame's address in the file, and asks the server for that frame. Ask Claude to run whoami to see which Figma account, plans and seat it is using.
| Command | What it does |
|---|---|
claude mcp list | Lists your servers with their health, such as Connected or Needs authentication |
claude mcp remove figma | Removes the server |
/mcp in a session | Opens the server list. Choose Re-authenticate to sign in again |
Connect it to the Claude app and other clients
Claude Desktop and claude.ai use a connector, not a command. Open Customize, then Connectors, select Discover, search for Figma, select Connect to Claude and sign in to Figma. On Team and Enterprise plans an Owner adds the connector first, and members then connect their own accounts.
On the connector's page you can set each tool to Always allow, Needs approval or Blocked. If you are logged in to Claude Code with the same Claude account, the connector also appears in its /mcp list. If you also added the same URL by command, that server wins and /mcp shows the connector as hidden.
Only clients in Figma's MCP catalog can connect, and each asks you to sign in to Figma. These five can all write to the canvas through the remote server:
| Client | How to add the remote server |
|---|---|
| Claude Code | The plugin or claude mcp add, above |
| Claude Desktop | The Figma connector in Customize, Connectors |
| Cursor | Type /add-plugin figma in the chat |
| Codex CLI | codex mcp add figma --url https://mcp.figma.com/mcp |
| VS Code | The one-click install, or an mcp.json entry with the same URL |
How these editors compare is in our AI code editors guide.
Remote or desktop server
Figma recommends the remote server for almost everyone. It lives at https://mcp.figma.com/mcp. The desktop server runs at http://127.0.0.1:3845/mcp and is for specific organization needs. Older guides call it the Dev Mode MCP server.
| Remote | Desktop | |
|---|---|---|
| Needs the Figma app | No | Yes, with a Design file open in Dev Mode |
| Seat | Any, with call limits | Dev or Full, not on Starter |
| Writes to Figma | Yes, with use_figma | No |
| Code to canvas | Yes | No |
| Tools in our session | 33, plus 9 for Weave | 10 |
What the tools do today
You usually do not need to name a tool. Claude picks one from what you ask, and if it picks wrong you can say exactly what you want. They fall into jobs:
| Job | Tools |
|---|---|
| Read a design: code, an outline, a picture, the variables used, animation keyframes | get_design_context, get_metadata, get_screenshot, get_variable_defs, get_motion_context |
| Export assets and read FigJam: up to 20 nodes per call as PNG, JPG, SVG or PDF | download_assets, get_figjam |
| Find your design system: libraries, components, variables, styles | get_libraries, search_design_system |
| Connect to code: read and add Code Connect mappings, the links from components to code | get_code_connect_map, add_code_connect_map |
| Write to Figma: frames, components, variables, auto layout, files, images | use_figma, create_new_file, upload_assets |
| Send code to Figma: a live web UI, an HTML file or a project | generate_figma_design, html_to_figma, send_code_to_figma |
| Draw diagrams: flowcharts, Gantt, state, sequence, architecture, ER | generate_diagram |
| Check your account: email, plans, seat | whoami |
Everything from Write to Figma down needs the remote server, as do download_assets and the library search. get_design_context returns React and Tailwind code, a common web format, unless you ask for another framework. There are also tools that generate images with Figma AI credits, tools for generative plugins and shaders, and tools that run Figma Weave, added on 26 October 2026.
What we counted
In our own Claude session on 6 November 2026, the Figma connector listed 42 tools: 33 of Figma's and nine for Weave. The desktop server in the same session listed 10, and none of them writes to the canvas. Three connector tools, create_session, get_figma_skill and export_video, were not in Figma's docs table yet, and two tools from the table, generate_figma_design and html_to_figma, were not in the connector.
Here is the lightest read, get_metadata, run on the cover frame of this guide (trimmed):
<frame id="38:2" name="cover/figma-mcp-guide" ...>
<text id="38:3" name="title" x="60" y="98" ... />
...
</frame>
That is only an outline of IDs, names, types, positions and sizes. Claude then asks get_design_context for the parts it needs.
Skills make it reliable
Tools are what Claude can do. Skills are written instructions, saved as Markdown files, for doing it well: which steps to take, in what order. Figma's advice is to start with figma-use and add others beside it. The plugin installs them, and the Figma connector in our session also listed a get_figma_skill tool and 16 skills.
| Skill | Use it to |
|---|---|
figma-use | Write to a Design file with use_figma. The base the others build on |
figma-design-to-code | Implement a frame as code. The connector tells Claude to load it before get_design_context |
figma-generate-design | Build a screen in Figma from code or a description, with your components and variables |
figma-generate-library | Build or update a component library and variables from a codebase |
figma-code-connect | Map published components to their code |
figma-spec | Read and update Figma Specs, which are in open beta |
Prompts that work
Bad
Build the pricing page from my Figma.
There is no link, so the remote server does not know which file or layer to read.Good
Implement this design: [link to selection]
The link gives the server the node. Right-click a frame, choose Copy link to selection and paste it.Great
Implement [link to selection] using components from src/components/ui.
Claude only knows your conventions if you say so, or if Code Connect, variables or rules carry them. Name the folder.
More on wording your asks is in prompt engineering for designers.
Writing to Figma, in beta
Since 24 March 2026 the remote server can write. With the use_figma tool Claude runs code in your file through the Figma Plugin API and builds frames, components, variables and auto layout from your own libraries. It is free during the beta and will become a usage-based paid feature.
- Who can use it: a supported client on the remote server, edit access to the file, and a Professional, Education, Organization or Enterprise plan. A Full seat is needed outside your drafts. A Dev seat writes in drafts only.
- Limits: each tool call returns up to 20 KB.
use_figmacannot add new images itself, so Claude usesupload_assets. Fonts must be uploaded to your Figma account. Output is beta quality and may need cleanup. - Skills: Figma says you need both the tool and the
figma-useskill, which the plugin installs. - Figma's advice: test on a duplicate or a draft, and keep a backup.
We built the cover of this guide this way. Claude duplicated a frame in our cover file, swapped the title, built the Figma logo as vector layers from SVG paths and checked it with get_screenshot, in seven use_figma calls (four to read, three to build and fix) and three screenshots. Placing one tag took two corrections: it first hid behind a card, then sat on top of the logo.
Limits and plans
Limits apply to the tools that read from Figma, by plan and seat.
Starter plan, or a View or Collab seat on any plan
Professional, Full or Dev seat
Organization, Full or Dev seat
Enterprise, Full or Dev seat
Per-minute caps apply too: 10 on Professional, 15 on Organization and 20 on Enterprise. Education plans match Professional. Some tools do not count, among them add_code_connect_map, create_new_file, generate_figma_design and whoami. Image generation uses Figma AI credits, Weave tools use Weave credits, and Figma may change the limits at any time.
Security
- Access follows your account. The server only reaches files you can already open. To revoke it, open
/mcp, select the server and choose Clear authentication. - The remote server runs on Figma's side. Only the desktop server runs on your machine, at
127.0.0.1. - What the server returns goes to the model. Layer names, text, variables and screenshots join the conversation, so treat a confidential frame like any file you paste into a chat.
- Treat files you did not write as untrusted. Claude Code's docs warn that servers which fetch external content can expose you to prompt injection, which is text that tries to steer the model. Text in a stranger's Figma file is content Claude reads.
- Gate the write tools. In the Claude app, set
use_figmato Needs approval. Enterprise teams can use Okta Cross App Access, a single sign-on setup, so people sign in once for Claude.
When it breaks
| What you see | Why, and what to do |
|---|---|
use_figma is missing | Your client loaded the desktop server. Remove its 127.0.0.1:3845 entry and restart |
| "exceeds maximum allowed tokens (25000)" | The frame is bigger than Claude Code's default limit for one tool result. Select a smaller layer, or raise the limit as shown below |
| A file cannot be accessed | Wrong account, or no access to the plan that owns the file. Ask Claude to run whoami |
| Images stop loading | The server hosts images temporarily. Ask for the design again, or save the images into your project |
| It always returns React | The server describes designs in a form that looks like React and Tailwind. Name your framework or components, or set up Code Connect |
| "Needs authentication" | Your sign-in is missing or expired. Open /mcp and choose Authenticate, or Re-authenticate if you signed in before |
To raise the token limit, run export MAX_MCP_OUTPUT_TOKENS=50000 in the terminal you start Claude Code from. In Windows PowerShell, use $env:MAX_MCP_OUTPUT_TOKENS=50000. A big frame also eats your context, which Claude Code context management covers.
FAQ
How do I connect Figma MCP to Claude Code?
Run claude mcp add --transport http figma https://mcp.figma.com/mcp, start a new session, type /mcp, select figma, choose Authenticate and allow access. Figma's plugin, claude plugin install figma@claude-plugins-official, adds the same server plus skills.
What is Figma MCP?
It is Figma's official server for the Model Context Protocol, the open standard Anthropic released in November 2024. It lets an AI agent read layout, variables and components and, on the remote server, write to them.
Is Figma MCP free?
Figma lists no separate server fee, but calls are capped: 20 a month on Starter and View or Collab seats, 200 a day on a Professional Full or Dev seat. Writing to the canvas is free in beta and will become usage-based, and image generation uses AI credits.
Figma MCP vs Figma plugin: what is the difference?
A plugin runs in an open Figma file, started by a person. Figma MCP lets an AI agent in another app call tools on your files from a link. The two meet in use_figma, which runs the Plugin API code that plugins use in your file. Figma's Claude Code plugin is a third thing: an installer for the server settings and skills.
Does Figma MCP work with Claude Desktop?
Yes. Add the Figma connector under Customize, Connectors and sign in to Figma. Code to canvas, which captures your app's UI, is not on Figma's list for Claude Desktop.
Can Claude edit my Figma file?
Yes, through use_figma on the remote server. You need edit access, and a Full seat outside your drafts. It is a beta: test on a duplicate.
How do I send my app's UI into Figma?
Ask Claude Code: "Start a local server for my app and capture the UI in a new Figma file." The generate_figma_design tool turns it into editable layers. For an HTML file use html_to_figma, for a project send_code_to_figma. It needs the plugin or the claude mcp add server, not the Claude app connector.
Sources
- Figma developer docs, checked 6 November 2026: remote server, desktop server, tools and prompts, write to canvas, code to canvas and rate limits and access.
- Figma Help Center: Figma MCP server FAQs, Figma skills for MCP and Claude Code and Figma.
- Figma blog: Introducing our MCP server, 4 June 2025, and Agents, meet the Figma canvas, 24 March 2026.
- Figma, release notes, 26 October 2026: Weave through the Figma MCP. Plugin API introduction and figma/mcp-server-guide on GitHub.
- Claude Code docs, Connect Claude Code to tools via MCP, and Claude docs, Get started with connectors.
- Anthropic, Introducing the Model Context Protocol, 25 November 2024.
- Our checks on 6 November 2026: the tool list of the Figma connector (42 tools), its skill index (16 skills) and the desktop server's tool list (10), read in one Claude Code session, and the cover of this guide built through
use_figmain our own Figma file.
Want Figma MCP wired into your team's workflow without the setup headaches? Brainy installs it end-to-end.
Get StartedGet new papers by email
New Brainy papers in your inbox. Confirm once, unsubscribe anytime.





