What does the Figma MCP server give a coding agent, and which seat do you need?

Short answer

Figma's MCP server gives coding agents such as Claude Code, Cursor, Codex and VS Code a frame's design context: variables, components, layout and Code Connect mappings. The remote server at https://mcp.figma.com/mcp is recommended, on all plans. As of November 2026, read calls are limited per seat: 20 a month for View and Collab seats, and 200 to 600 a day for Dev and Full seats on paid plans.

What the agent gets from Figma

Without Figma access, a coding agent works from a screenshot or a description and guesses the spacing, colors and components. The Figma MCP server lets it read the design itself. According to Figma’s guide it can:

  1. Generate code from selected frames.
  2. Extract design context: variables, components and layout.
  3. Retrieve resources from FigJam and Figma Make.
  4. Use Code Connect, which maps Figma components to the components in your codebase, so the agent uses your real Button instead of writing a new one.

In beta, agents can also write to the canvas, for example to create a new file or turn code into a design.

Figma’s tool reference adds two practical details. By default get_design_context returns React and Tailwind, and you can ask for another framework in your prompt. For large designs, call get_metadata first: it returns a lightweight XML outline, useful when get_design_context would return too much at once. Prompting with your current selection only works with the desktop server; with the remote server, include a link to the frame or layer.

Remote or desktop

Remote server Desktop server
Where https://mcp.figma.com/mcp (government: https://mcp.figma-gov.com/mcp) Through the Figma desktop app
Figma’s advice Recommended For specific organization and enterprise needs
Seat All plans Dev or Full seat on Professional, Education, Organization, Government or Enterprise
Write to canvas Yes (beta) No

Figma’s client table includes Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, VS Code and Xcode. For how to add a remote server per tool, see MCP servers in Claude Code for a team or Cursor MCP servers.

Rate limits, as of November 2026

Limits apply to tools that read from Figma. Writing tools are exempt.

Seat Starter Professional Organization Enterprise
View, Collab 20 a month 20 a month 20 a month 20 a month
Dev, Full n/a 200 a day, 10 a minute 200 a day, 15 a minute 600 a day, 20 a minute

This is the detail that catches teams out. A developer on a View seat who tries the MCP server runs out after 20 read calls in a month, and an agent working through a screen may call more than one read tool. If developers are going to build from Figma with an agent, budget Dev seats for them.

The common misunderstanding

“The agent can now build our UI from Figma.” It can read the design. Whether the output fits your codebase depends on things Figma does not hold: which component library you use, how you name things, which patterns your team rejected. Code Connect closes part of that gap by mapping design components to code components, but someone has to set those mappings up and keep them current. The rest, such as “we never use inline styles” or “forms always go through our validation hook”, lives in your repo’s rules and in reviewers’ heads.

What this means for a team

The Figma MCP server is worth it for teams where design and code meet daily. Three practical points:

  1. Give developers who use it a Dev seat, or the 20-a-month limit ends the experiment early.
  2. Invest in Code Connect for your core components; that is where the output starts to look like your code.
  3. Put the remote server in the shared project config so every developer and every tool connects the same way.

What Figma does not carry is what each developer’s agent learned while turning designs into code. A correction made in one person’s session does not reach the next. See shared memory across coding agents, and for the basics what is an MCP server.

Where Bombos fits

Figma gives the agent the design; Bombos gives every AI tool in the team the same memory of how you build it. It is a plugin for Claude Code, Cursor, Codex, Copilot and your other AI tools, with team knowledge, rules the AI learned from corrections, and what already sits in repos, documents and mail, with a trail of what each answer rests on. It runs in our cloud or on your own server, and one developer can try it first with their own agents.

Related questions

Do I need the Figma desktop app for the MCP server?

No. The remote server at https://mcp.figma.com/mcp works without it and is the one Figma recommends. The desktop server runs through the Figma desktop app and is meant for specific organization and enterprise needs.

Which seat do I need for the Figma MCP server?

Any seat can use the remote server, but View and Collab seats get up to 20 read calls a month. Dev and Full seats on Professional, Organization or Enterprise get daily limits of 200 to 600. The desktop server needs a Dev or Full seat on a paid plan.

Can the AI write to Figma files?

Yes, in beta. Writing to the canvas needs the remote server and a Full seat to write outside your drafts. Figma says it is free during the beta and will become usage-based.

Do write tools count against the rate limit?

No. Figma's limits apply to tools that read from Figma; tools that write, such as generate_figma_design and add_code_connect_map, and whoami are exempt.

Sources

  1. Guide to the Figma MCP server (Figma Help Center)
  2. Rate limits & access (Figma developer docs)
  3. Tools and prompts (Figma developer docs)
The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.