What it is
Figma recommends its remote server at https://mcp.figma.com/mcp, which needs no desktop app and has the full feature set. A desktop server runs through the Figma desktop app for organisations that need it, requires a Dev or Full seat on a paid plan, and lacks most write tools. Figma for Government supports the desktop server only.
The tools page lists 32 core tools: 18 read tools, including get_design_context (React and Tailwind by default), get_metadata, get_screenshot, get_variable_defs and search_design_system, and 14 write tools, including use_figma, generate_figma_design, generate_diagram, html_to_figma and create_new_file. Figma Weave tools are listed separately.
Code Connect mappings keep generated code in line with your components, and the figma-spec skill lets agents read and update Figma Specs, which is in open beta. Writing to the canvas needs a Full seat outside your drafts; it is free during the beta and Figma says it will become a usage-based paid feature.
Install
https://mcp.figma.com/mcpOur review
For moving designs into code, Figma's own server is the one that matters, because it has access no third-party server can match. get_design_context returns structure, styles, variables and code for a selection, Code Connect points the agent at your real components, and get_metadata gives a lightweight XML outline so the agent can fetch only the parts of a large frame it needs. The client table lists more than 20 supported tools, from Claude Code and Codex to Cursor, VS Code and Xcode in beta.
The write side is newer and remote-only. use_figma creates and edits frames, components, variables and auto layout; generate_figma_design turns live web UI from production, staging or localhost into editable layers; generate_diagram builds FigJam diagrams from a description or Mermaid. Figma recommends installing its skills before using these tools, which says something about how reliably agents use them unaided.
Rate limits are the constraint a buyer will feel. Full and Dev seats get 200 read calls a day on Professional (10 a minute) and Organization (15 a minute), and 600 a day on Enterprise (20 a minute). Starter accounts, and View or Collab seats on any plan, get 20 calls a month, which rules out handing the server to the wider company on cheap seats. Write tools are exempt, but generate_image and the Make prompt tool spend Figma AI credits.
Two plan details are easy to miss. On Professional only one Code Connect framework can be active, so a team with React and SwiftUI codebases gets mappings for one; Organization and Enterprise allow several. Enterprise-managed sign-in exists only for Claude, through Okta Cross App Access. Against Canva's server, this one is narrower in audience and far deeper for product teams.
Where it earns its place
A front-end engineer on a React team using Claude Code
Build approved screens from Figma using the team's own component library
Pastes a frame link; the agent calls get_metadata, then get_design_context on each section with Code Connect mapped to src/components. A Dev seat at $12 a month on Professional covers it, with 200 read calls a day as the ceiling.
A design-systems lead at a 40-designer fintech on Enterprise
Keep the Figma library and the coded components in step
Uses the figma-code-connect skill to suggest and confirm mappings, and use_figma to update variables when tokens change in code. Enterprise's 600 calls a day per seat leaves room for library-wide passes; writes are free during the beta.
A product manager at a 15-person startup
Turn the live staging site into editable frames to mock up a change
Asks the agent to run generate_figma_design on the staging page, then edits the layers directly. It needs the remote server and a Full seat ($16 on Professional), and Figma plans to charge for canvas writing after the beta.
Before you commit
- Setup
- Add https://mcp.figma.com/mcp to the client and sign in with OAuth; Claude Code, Cursor, VS Code and Copilot CLI have a Figma plugin, Codex has skills. The remote server takes a frame link, not your current selection.
- Integrations
- 32 core tools: 18 read (get_design_context, get_metadata, get_screenshot, get_variable_defs, download_assets, search_design_system) and 14 write (use_figma, generate_figma_design, generate_diagram, html_to_figma, upload_assets).
- Data and privacy
- The server reaches only files your account can already open, and the hosted server processes them on Figma's side. Figma's MCP introduction, tools and limits pages do not discuss prompt injection from file content; Okta XAA is supported for Claude only.
- Cost at scale
- No server fee. A 20-engineer team on Organization pays $25 a Dev seat, $500 a month, for 200 read calls each a day; at five calls a screen that is about 40 screens per engineer a day. Image and Make tools also spend AI credits.
- Limits
- Per-minute caps of 10, 15 or 20 calls by plan on top of daily limits; download_assets handles 20 nodes per call; one active Code Connect framework on Professional; Figma may change limits at any time.
What's good
- Structured design context and Code Connect mappings, not just images
- get_metadata keeps large frames from flooding context
- Write tools for frames, components, FigJam and live-UI capture
- Hosted with OAuth; no desktop app needed
What's not
- 200 read calls a day per Full or Dev seat below Enterprise
- View, Collab and Starter get 20 calls a month
- Most write tools missing from the desktop server
- Canvas writing will become a paid, usage-based feature
Best for
Front-end engineers and design-system teams turning Figma files into code, and designers who want agents to draft into the canvas.
Alternatives
Figma MCP Server: common questions
- Is Figma MCP Server worth it?
- Figma's server gives coding agents structure rather than screenshots and now lets them draw back, but seat-based read limits decide how far a team can lean on it. We rate it 4.6 out of 5.
- How much does Figma MCP Server cost?
- Included with Figma plans. Read calls: 200 a day on Professional and Organization Full and Dev seats, 600 on Enterprise; Starter, View and Collab get 20 a month. Canvas writing free in beta.
- What are the downsides of Figma MCP Server?
- 200 read calls a day per Full or Dev seat below Enterprise; view, Collab and Starter get 20 calls a month; most write tools missing from the desktop server; canvas writing will become a paid, usage-based feature.
- Who is Figma MCP Server best for?
- Front-end engineers and design-system teams turning Figma files into code, and designers who want agents to draft into the canvas.
- How much does Figma MCP Server cost for a team or in production?
- No server fee. A 20-engineer team on Organization pays $25 a Dev seat, $500 a month, for 200 read calls each a day; at five calls a screen that is about 40 screens per engineer a day. Image and Make tools also spend AI credits.
- Is Figma MCP Server safe for company data?
- The server reaches only files your account can already open, and the hosted server processes them on Figma's side. Figma's MCP introduction, tools and limits pages do not discuss prompt injection from file content; Okta XAA is supported for Claude only.
- What are the best Figma MCP Server alternatives?
- The closest alternatives we have reviewed are Canva MCP Server, Chrome DevTools MCP and Playwright MCP.
Answers checked Oct 22, 2026.
Make Figma MCP Server? Show this rating on your site
