Figma MCP: 35 tools, the real limits, the missing layer

Search "figma mcp" and Google hands you six pages from figma.com, an AI Overview, and one Reddit thread. None of them puts the whole picture in one place.

Quick answer: The Figma MCP server is Figma's official Model Context Protocol server. It gives an AI coding agent structured access to a Figma file: layout and text, component properties, variables and styles, screenshots, Code Connect mappings, and, on the remote server, the ability to write back to the canvas. As documented on 11 September 2026 it exposes 35 tools plus one prompt. The remote server runs on all seats and plans, but Starter and View/Collab seats get a handful of tool calls per month while Dev and Full seats get hundreds per day. Everything it returns is scoped to the selection you point it at, which is why it fixes translation and not consistency. Figma knows this: it ships a separate prompt whose only job is to generate a rules file.

What Figma MCP actually is

Figma announced the server on 4 June 2025, then as the Dev Mode MCP server and explicitly a beta: "As a beta, this is only the beginning." Fifteen months later it is the thing most agentic coding tools reach for when they need to know what a screen is supposed to look like.

Google's AI Overview for the query now defines it as "an open standard integration using the Model Context Protocol that connects your Figma designs directly to AI coding tools and LLMs," and lists three jobs: reading design context, writing to the canvas, and generating code. That summary is fair, and it is worth knowing that Google built it partly from a r/FigmaDesign thread rather than only from Figma's docs.

There are two servers, and the difference matters more than the setup tutorials suggest:

• Remote server, the one Figma recommends. It "connects directly to Figma's hosted endpoint without requiring the Figma desktop app" and, per Figma's guide, "provides the broadest set of features." The endpoint is https://mcp.figma.com/mcp. Available on all seats and plans.
• Desktop server, which runs inside the Figma desktop app. Figma positions it for "specific organization and enterprise needs" and it is the only option for Figma for Government. It needs a Dev or Full seat on a paid plan.

One access rule catches people out: per Figma's developer docs, "Only clients listed in the Figma MCP Catalog can connect to the Figma MCP Server." The catalog currently lists 24 clients, including Claude, Claude Code, ChatGPT, Codex, Cursor, VS Code, GitHub Copilot CLI, Kiro, Grok, Google Antigravity, Xcode in beta, Zed, Warp, Devin, Replit, Notion, Slack, Android Studio and Amazon Q. If your tool is not on that list, Figma's answer is to "apply to register your client for remote access."

What the server exposes: 35 tools and one prompt

Figma documents the full set on the tools and prompts page. As of 11 September 2026 it is 18 read tools, 11 write tools, 6 Weave tools, and 1 prompt. Most write-ups name two or three of these. Here is the shape of the whole surface.

The read tools that do the actual work

Four of the 18 carry almost all of the design-to-code load:

1. get_design_context, "Design context for a layer or selection." This is the default entry point. Figma's own MCP server guide says it "provides a structured React + Tailwind representation of your Figma selection."
2. get_variable_defs, "Variables and styles used in a selection," which the same guide describes as extracting "the variables and styles used in your selection (color, spacing, typography, etc)."
3. get_metadata, "Sparse XML outline of a selection." The cheap overview: layer IDs, names, types, positions, sizes, no styling detail.
4. get_screenshot, "Screenshot of a selection," for when the agent needs to see the thing rather than read it.

The rest of the read set is narrower and more interesting than the tutorials let on: get_code_connect_map ("Retrieves node ID to code component mappings"), get_libraries ("Lists subscribed and available libraries"), search_design_system ("Searches libraries for components, variables, styles"), get_motion_context ("Keyframe animation data and code snippets"), get_figjam ("Converts FigJam diagrams to XML"), download_assets, whoami, plus shader and generative-plugin readers.

search_design_system is the one worth a second look. It searches across your libraries rather than the current selection, which makes it the only read tool that is not selection-scoped.

The write tools, which is the part most posts get wrong

The server writes now. Eleven tools do it: use_figma ("General-purpose create, edit, and inspect"), generate_figma_design ("Generates design layers from interfaces"), create_new_file, upload_assets, generate_diagram ("Generates a FigJam diagram from Mermaid"), add_code_connect_map, plus shader and generative-plugin writers.

Figma's guide frames the headline capability as "Let your agent write directly to the canvas in Figma Design and FigJam," and a second one as "Generate designs from the live UI of your web apps and sites," which turns a running page back into editable layers. Both carry conditions: canvas writing "requires the remote Figma MCP server," and UI capture "requires the remote Figma MCP server and is currently supported by select clients."

Six Weave tools

weave_list_tools, weave_get_tool_inputs, weave_upload_asset, weave_run_tool, weave_get_tool_run_output, weave_cancel_tool_run. These let an agent run Figma Weave tools from the chat and poll for results. Irrelevant if you do not use Weave, and the reason a raw tool count of 35 overstates what a typical front-end workflow touches.

The one prompt, which is the tell

Alongside the 35 tools, Figma ships exactly one prompt: create_design_system_rules, documented as "A prompt for creating a rule file that provides agents with the right context to translate designs into high-quality, codebase-aware frontend code."

Read that again. The company with the most complete machine-readable picture of your design work ships a prompt whose purpose is to produce a file that lives in your repo. Hold that thought until the limits section.

What it costs and where the ceilings are

"Is Figma MCP free" is one of the most asked questions on this SERP, and the honest answer is "it depends on your seat, and the free tier is a trial, not a workflow."

Per Figma's rate limits and access page, read-tool calls are capped like this:

Seat	Starter	Professional	Organization
View, Collab	Up to 20/month	Up to 6/month	Up to 6/month
Dev, Full	Up to 200/day, 10/min	Up to 200/day, 15/min	Up to 600/day, 20/min

Enterprise matches Organization, and Education follows the Professional tier. Three tools sit outside the limits because they write rather than read: add_code_connect_map, create_new_file and whoami.

Two things to flag honestly. First, Figma's two official sources do not agree: the docs table shows Starter View/Collab seats at 20 a month, while Figma's mcp-server-guide repo says "Users on the Starter plan or with View or Collab seats on paid plans will be limited to up to 6 tool calls per month." Check your own limit in the app before planning around either number. Second, canvas writing is "currently available for free during the beta period" and Figma says it will move to usage-based pricing later, so today's cost is not next quarter's cost.

Either way, the practical read is simple: 6 to 20 calls a month is enough to watch a demo. A real design-to-code session burns dozens of calls on a single screen, which is why the Dev or Full seat is the actual price of entry.

What Reddit reports, and what has changed since

r/FigmaDesign is where this gets litigated. The "figma mcp reddit" SERP is 24 of roughly 28 organic results on Reddit, so it is also what an LLM reads when someone asks whether this thing works. Quotes below are the snippets Google returns, linked to the threads.

It lands well when the file is clean. Have you used the Figma MCP? Has it helped you at all? (20+ comments): "Figma MCP is a game changer for me. It's making me feel like I can design relatively complex applications and develop them myself with an LLM."

It lands badly when people expect a designer. is designing with Claude/MCP and figma even practical? (60+ comments): "I tried it when it came out, it seems so anticlimactic... It's like a junior junior designer that doesn't really know what he's working on."

Fidelity is the recurring complaint. Best way to accurately implement figma designs with LLM (60+ comments): "I have tried implementing figma designs with VScode+Figma MCP, but they never turn out to be very good." In Struggling to maintain Figma design fidelity with Claude (20+ comments) the opening line is "I've been experimenting with using Claude Code and the Figma MCP to build out an app onboarding flow, but I'm running into some massive issues."

Chattiness costs tokens. Claude code + Figma mcp (30+ comments): "Claude (Code) has to do a LOT of back and forth via the Figma MCP when trying to do anything beyond trivial work that requires making changes in ..." Figma's own guide names the same failure from the other side: "Large selections can slow the tools down, cause errors, or result in incomplete responses, especially when there's too much context for the model to process."

The read-only threads are now out of date, and they still rank. Figma prep for two-way MCP (20+ comments) states "The official Figma MCP does only read from Figma. If you want both ways, you will also need to use the official Claude Integration or a Plugin ...". Unofficial Figma MCP server (30+ comments) says "We found that the official Figma MCP server is only one-way. It provides data from the Figma design document, but it can not change it." A whole genre of write-enabled alternatives grew out of that gap, including a write-enabled server built on raw JavaScript ("Instead of adding tons of MCP tools, it lets the AI write and run JavaScript directly with the Figma API. Fewer tokens, easier batching, and way ...") and Figwright ("The official MCP server only reads Figma into code, while Figwright can also write back to the canvas."). The biggest of them, Framelink MCP for Figma, has 15.8k GitHub stars on the premise that "Reducing the amount of context provided to the model helps make the AI more accurate and the responses more relevant."

If you are reading those threads for a buying decision in September 2026, check the dates. The official server writes to the canvas now. The correction arrives in a newer thread, Claude Code & Figma MCP: Free plan or Paid plan? (10+ comments): "If you want to let claude code edit your design, choose figma remote MCP + a paying plan. Desktop MCP won't let claude code edit the design."

And the design-system question keeps going unanswered. MCP & design systems, am I missing something? (20+ comments) opens with "Lately been seeing some movement around design systems and the mcp, but seems like I cannot get the full picture of it." That thread is the honest version of what most people actually want to know, and it is the next section.

What the server structurally cannot give your agent

This is not a knock on Figma. It is a property of what a file is.

Almost every read tool is selection-scoped. get_design_context, get_variable_defs, get_metadata, get_screenshot and get_motion_context all answer the question "what is in this frame." Point them at a dashboard card and you get that card, faithfully: its tokens, its layout, its text, its variants.

What no tool answers is the question a good front-end engineer asks before writing anything:

• Which of our three button variants is correct here, and when is the ghost variant wrong?
• Is this 18px gap intentional or a drift from the 4px spacing scale?
• What are the loading, empty, error and disabled states for this table, given that none of them were drawn?
• Which chart colors are allowed together, and in what order?
• What is our rule for dense data, 13px or 14px, and does it change on mobile?

Those are not in the frame. They are conventions that live in a design lead's head, in a Notion page, or nowhere. A designer reading the same file supplies them from memory. An agent supplies a plausible guess, and plausible guesses are exactly how one product ends up looking like four different products stitched together.

The practitioners closest to this describe the same edge. Christine Vallaure, in a LinkedIn post from 4 September 2026, opens: "An agent reading your Figma file over MCP sees more than most designers assume, and misses things nobody warns you about." Her list of what comes through starts with variables: names, values, every mode. The misses are the part nobody documents.

And Figma agrees, in the plainest way a company can: it tells you to write the rules down. Its MCP guide says "Set project-level guidance to keep output consistent", with example rules like "Reuse existing components (e.g., buttons, inputs, typography, icon wrappers) instead of duplicating functionality." Then it ships create_design_system_rules, a prompt that exists solely to generate that file.

That file is the missing layer. The MCP server translates a selection. The rules file governs every selection. You need both, and only one of them comes out of Figma.

Getting more out of it

✅ Do this

• Use a Dev or Full seat. The free allowance is a demo budget, not a workflow.
• Select one frame or section at a time. Figma's own guidance is that large selections cause slow, erroring or incomplete responses.
• Set up Code Connect before you judge output quality. Figma's own measurement, published 5 August 2026, reports that with Code Connect in MCP "Token usage for the median task was reduced by 29.5%", "The median task duration was reduced by 19.6%", and "Code quality increased by a full point on a Likert scale of 1–4."
• Name layers semantically and use variables rather than raw hex. A practitioner reel that Google surfaces on this query puts it as "If your code comes out looking nothing like your design, it's usually a few things you skipped in the file, not the tool," and lists "Clean layers. Auto layout, semantic names." and "Figma variables so your tokens carry into the build."
• Keep a project rules file in the repo and make the agent read it on every task.

❌ Avoid this

• Selecting a whole page and expecting a component architecture back.
• Treating the screenshot tool as a substitute for tokens. An image tells the model what it looked like, not what the rule was.
• Assuming a 2025 or early-2026 Reddit thread describes today's server. Read-only stopped being true.
• Buying a paid Figma seat to fix inconsistency. Inconsistency is a specification problem, not an access problem.
• Letting the agent invent states. Draw them or write them down, or it will guess.

Where a DESIGN.md fits

A DESIGN.md is the rules file, written once for the product rather than regenerated per repo. It carries the things the MCP server cannot: the full token set with names and values, the type and spacing scales, elevation and radius rules, component usage constraints, state coverage, and the do-not-do list. It is plain markdown, so every agent in the catalog reads it with no server, no seat and no rate limit.

The two layers compose cleanly:

1. Figma MCP answers "what is this screen." Layout, variables, component props, Code Connect mappings for the selection in front of it.
2. DESIGN.md answers "what are our rules." Which variant, which scale step, which states, which combinations are banned, across every screen.

Point your agent at both and the failure mode changes. Instead of a faithful copy of one frame and a guess at the next nine, you get nine screens that agree with each other.

The duply library has DESIGN.md files extracted from real shipped products, so you can see the format before writing your own. Linear is the reference for dense product UI, Stripe for data-heavy dashboards, Vercel for restrained dark interfaces. Drop one in your repo root, tell your agent to read it before it touches the Figma MCP, and compare the output to your last session. The full workflow is in how to give your AI agent a design system.

FAQ

What is Figma MCP for? It gives AI coding agents structured access to your Figma files so they can generate code that matches the design, and, on the remote server, create or modify Figma content from the agent. It replaces pasting a PNG into a chat window with a real data connection to layout, text, component properties, variables and styles.

Is Figma MCP free? Partly. The remote server is available on all seats and plans, but read-tool calls are capped: Starter and View or Collab seats get between 6 and 20 calls per month depending on which Figma source you read, while Dev and Full seats get 200 to 600 per day. Canvas writing is free during the beta and Figma says it will become usage-based. For practical work you need a Dev or Full seat.

What is the rate limit for Figma MCP calls? Per Figma's docs: Starter Dev/Full up to 200 a day and 10 a minute, Professional Dev/Full up to 200 a day and 15 a minute, Organization and Enterprise Dev/Full up to 600 a day and 20 a minute. View and Collab seats get 6 a month on paid plans and 20 a month on Starter. add_code_connect_map, create_new_file and whoami are exempt.

Do you need Dev Mode for Figma MCP? Not any more in the way the older articles imply. The server launched as the Dev Mode MCP server in June 2025, but the recommended path today is the remote server at https://mcp.figma.com/mcp, which works on all seats and plans without the desktop app. The desktop server is the one that requires a Dev or Full seat on a paid plan.

Can I use Claude Code with Figma as an MCP? Yes. Claude and Claude Code are both listed in the Figma MCP Catalog, and Figma publishes a dedicated Claude Code setup article. Per r/FigmaDesign, if you want Claude Code to edit the design rather than only read it, you need the remote server plus a paid plan.

Is there an MCP plugin for Figma? The official integration is a server, not a plugin, and only clients listed in the Figma MCP Catalog can connect to it. There is a large ecosystem of unofficial servers built on the Figma API, the biggest being Framelink MCP for Figma at 15.8k GitHub stars, most of which exist because the official server was read-only for its first year.

What are Figma skills for MCP? Figma's MCP catalog documents prompts and skills as the way to steer an agent once it is connected. The documented prompt is create_design_system_rules, which generates a rule file giving agents "the right context to translate designs into high-quality, codebase-aware frontend code." A DESIGN.md is the same idea maintained by hand rather than regenerated.

How many tools does the Figma MCP server expose? 35 as documented on 11 September 2026: 18 read tools, 11 write tools and 6 Weave tools, plus 1 prompt. In a typical front-end session you will touch four of them.

Does Figma MCP fix AI-generated UI looking generic? On one screen, largely yes, because the agent reads your real variables and components instead of guessing. Across a product, no. Consistency comes from rules that apply to every screen, and those are not stored in any single frame, which is why Figma tells you to keep project-level guidance in your repo.

Summary

• The Figma MCP server exposes 35 tools and 1 prompt as of 11 September 2026: 18 read, 11 write, 6 Weave
• Four read tools carry the workflow: get_design_context, get_variable_defs, get_metadata, get_screenshot
• The remote server at https://mcp.figma.com/mcp works on all seats and plans; the desktop server needs a Dev or Full seat on a paid plan
• Real limits: 6 to 20 read calls a month on Starter and View/Collab seats, 200 to 600 a day on Dev and Full seats
• Code Connect is the highest-leverage setup step, with Figma measuring 29.5% fewer tokens and a full point of code quality on a 1 to 4 scale
• Reddit's read-only complaints are now out of date, and the design-system question in those threads is still unanswered
• Every read tool is selection-scoped, so the server translates screens and cannot enforce rules. That takes a DESIGN.md your agent reads on every task

Give your agent both. Start with the duply library.

Related reading

• Mobbin MCP: what it gives your AI agent, and what it can't
• Figma to code: what Reddit says actually works (and breaks)
• What are design tokens? The agent-readable definition
• How to give your AI agent a real design system