Figma MCP rate limits: what they are, and what to do when you hit one

By Sabarish Sanjay, maker of Crossfade · Updated 7 November 2026

Figma limits how often an agent can read your files through its MCP server. The limit depends on your plan, your seat and, less obviously, on who owns the file. Here's the whole picture, checked against Figma's docs on 7 November 2026.

The limits, by plan and seat

Education plans get the same limits as Full and Dev seats on Professional. Per-minute limits apply on top of the daily or monthly ones, and Figma says it may change these at any time.

What counts as a call

Limits apply to tools that read data from Figma. Figma lists some exempt tools, including tools that write to files, such as add_code_connect_map, create_new_file, generate_figma_design and whoami.

That sounds generous, but agents work in loops. A careful agent reads the file, makes a change, takes a screenshot, checks it and reads again. Each look is a read, so a single screen can use a lot of calls, and 10 a minute can run out before a task is finished.

Why a paid seat can still get the Starter error

This is the one that catches people out. You see something like this, even though you pay for a seat:

You've reached the Figma MCP tool call limit on the Starter plan.

On Figma's forum, staff explained that limits attach to the team that owns the file you're reading, not to your account or your best seat. whoami reports your highest seat across everything, so it can say Pro while the file itself sits in your drafts or in a Starter team.

What to do when you hit a limit

1. Check where the file lives. If it's in your drafts or a Starter team, move it into your paid team and try again.
2. Run whoami. It's exempt from the limits, and it confirms which account, plan and seat your client signed in with.
3. Look for retry loops. An agent that repeats a failing call can burn through a small allowance quickly. Stop it and read the error.
4. Don't look at your AI credits. They're separate, so a healthy credit balance tells you nothing about your MCP allowance.
5. Ask for less at a time. Point the agent at one frame rather than a whole page, so it needs fewer reads.
6. Change your seat or plan. Figma's own advice is a Full or Dev seat on a paid plan, or Enterprise for 600 a day.
7. Contact Figma if it still looks wrong. Staff can't review your usage in public on the forum, so use support for your count and reset date.

Or work around the limit entirely

These limits belong to Figma's MCP server, not to Figma itself. A plugin running in your open file uses the Plugin API, so its reads never reach that server. That's how Crossfade, which I make, and several free tools work. This comparison covers them all fairly. The catch is that a plugin needs the Figma desktop app open.

Common questions

How many MCP calls do you get on Figma's Starter plan?

Up to 20 tool calls a month. Figma's staff have confirmed that this allowance is separate from Figma AI credits.

Why do I get the Starter limit error on a paid seat?

Figma's staff say limits attach to the team that owns the file you're reading, not to your account or your best seat. A file in your drafts or in a Starter team can get the Starter limit even when your account has a paid seat.

Do writes count towards Figma's MCP rate limit?

Figma's docs say limits apply to tools that read data, and that some tools are exempt, including tools that write to Figma files. Agents usually read a lot while they write, so a writing session still uses up reads.

Do Figma AI credits raise my MCP limit?

No. They're separate. Having credits left doesn't mean you have MCP calls left.