Figma MCP rate limits by seat, reset time, and workarounds

The Figma MCP rate limit depends on your seat and plan. View and Collab seats, and everyone on Starter, get up to 20 read tool calls a month. Dev and Full seats get 200 a day on Professional and Organization, and 600 a day on Enterprise, with a per-minute cap on top. Write tools are exempt, and Figma's docs do not say when the counters reset. This guide gives the numbers, what is unclear, and how to keep working when your agent hits "rate limit exceeded". Every Figma figure was checked on 2026-10-11 and is linked at the end. Figma can change its limits, so check the source first.

What are the Figma MCP rate limits?

Figma's docs list the limits by seat type and plan. A per-minute limit applies in addition to the daily or monthly one.

A few notes on reading the table:

• The Starter column shows one cell of "Up to 20/month" that spans both seat rows. In the docs, a Starter plan is described as "20 tool calls per month" with no per-seat split, so a Dev or Full seat on Starter has the same 20 a month.
• Education plans use the same limits as Dev and Full seats on Professional: up to 200 a day and 10 a minute.
• The limits apply to tools that read data from Figma. Figma's docs say some tools, such as those that write to Figma files, are exempt.
• Figma reserves the right to change rate limits.

The docs also name three exempt tools: add_code_connect_map, create_new_file, and whoami. The docs say exempt tools "include" these three, so the list may not be complete.

Why did I get "rate limit exceeded"?

Your agent made more read calls than your seat and plan allow for the day, the month, or a single minute. Agents make many reads. A loop that reads every frame in a flow, then scans text and variables, adds up quickly.

The seat matters more than most people expect. On Starter, or on a View or Collab seat, the allowance is 20 calls for the whole month. A single agent task that reads several frames can use that up.

Figma's docs do not describe the text of a rate limit error, so this guide does not quote one. Check your seat and plan first. The exempt whoami tool returns the email you authenticated with and the plans and seat types that account belongs to.

When does the Figma MCP limit reset?

Figma's docs do not say. They describe the limits as "per day", "per month", and "per minute". They do not say whether the day is a calendar day in a particular time zone or a rolling 24 hours, whether the month follows the calendar or your billing date, or whether the per-minute limit is a rolling window.

So "try again tomorrow" is a reasonable guess for a daily limit, but it is not a documented guarantee. For the 20-a-month tier, the docs give no reset date at all. If you need the exact time, ask Figma support.

Is the Figma MCP server free?

Partly. Figma's Help Center says the remote server is available on all seats and plans, so you can connect without paying for anything extra. What changes is how much you can read:

• On a free Starter plan, you get up to 20 read calls a month.
• On View and Collab seats of paid plans, it is also 20 a month.
• Dev and Full seats on paid plans get the daily allowances in the table above.
• The desktop server, which runs through the Figma desktop app, is available on a Dev or Full seat.

Writing to the canvas has its own rules. Figma's Help Center says write to canvas is currently free during its beta and "will eventually be a usage-based paid feature". The write-to-canvas docs say you need a Full seat to write to Figma files with agents, and that Dev seats are read-only. You also need edit permission for the file.

So connecting is free, reading is metered by seat, and writing is free for now but needs a Full seat.

What does the official Figma MCP server do well?

First-party support. Figma builds and maintains it, so it follows changes to the product and the file format.

Code Connect. When your components are mapped with Code Connect, Figma's server can include real implementation details from your codebase in what it returns. Canvashand does not replace that.

No install. The remote server connects to Figma's hosted endpoint without the desktop app, and Figma recommends it over the desktop server.

Writes are exempt. The metering applies to reads. An agent that mostly creates and edits can go a long way without touching the limit.

How do I keep working after hitting the limit?

You have four options. They are not exclusive.

1. Wait. Daily and per-minute limits are described as limits per day and per minute, so they should clear with time. Do not plan a deadline around an exact reset hour.

2. Spend fewer reads. Ask the agent to read one frame instead of a whole page, and to reuse what it already read. This stretches 200 a day. It does little for 20 a month.

3. Move up a seat or plan. Figma's docs give the upgrade paths. From Starter, move to Professional, Organization, or Enterprise with a Full or Dev seat. From a View or Collab seat, move to a Full or Dev seat. From a Full or Dev seat on Organization, Enterprise raises the cap from 200 to 600 a day. If your team already pays for these seats, this is the cleanest fix.

4. Add a second MCP server that does not use Figma's MCP limits. This is where Canvashand fits.

Figma MCP without a Dev seat: how Canvashand works

Canvashand is a local MCP server (a CLI) plus a Figma plugin. Your AI client, such as Claude Code, Cursor, or Codex, talks to the server on your machine. The server talks to the plugin running inside the open Figma file, over 127.0.0.1. Calls do not go through the Figma REST API or through Figma's MCP server, so Figma's MCP limits in the table above do not apply to them.

That means:

• No Dev seat and no API token. The plugin works in any file you can edit. Canvashand does not grant edit rights a seat lacks. It works only where you could already edit the file in Figma.
• Figma desktop is required. The plugin runs inside the open file, so Figma desktop must be installed and the file open.
• 99 MCP tools. They cover reads and writes: nodes, pages, styles, variables, components, prototypes, bulk edits, and exports.
• Canvashand has limits of its own. The Free plan includes 2,000 Canvashand tool calls a month, and that count covers every tool, reads and writes. Pro is $6.99 a month or $69.99 a year with unlimited calls and no per-day or per-minute throttle. Every Pro plan starts with a 7-day free trial.

Your Canvashand dashboard shows how many calls you have left this month. For a direct feature comparison, including Code Connect, several open files, and rollback, read Canvashand vs the official Figma MCP server.

Two servers can sit in one client under different names. Let Figma's server supply Code Connect context and let Canvashand do the heavy reading and the canvas edits. When Figma's server runs out of calls, the agent can carry on through Canvashand.

Which option fits you?

If a Full seat covers your use, stay on the official server. It is first-party and needs nothing installed. If you are on a 20-a-month seat, or your agents loop over many reads, add Canvashand or move up a seat. See pricing for the exact Canvashand plans.

Next step

Install the CLI, connect your AI client, and import the plugin once. The setup page walks through all three steps, and there are client guides for Claude Code and Cursor.

Sources

• Rate limits and access, Figma Developer Docs: limits by seat and plan (20 a month; 200 a day at 10 a minute on Professional; 200 a day at 15 a minute on Organization; 600 a day at 20 a minute on Enterprise), Education limits, exempt tools, upgrade paths, whoami, Figma may change limits. The page does not state when counters reset. Checked 2026-10-11.
• Guide to the Figma MCP server, Figma Help Center: the remote server is available on all seats and plans; the desktop server is available on a Dev or Full seat; write to canvas is free during the beta and will become usage-based. Checked 2026-10-11.
• Write to canvas, Figma Developer Docs: a Full seat is needed to write to files, Dev seats are read-only, and edit permission on the file is required. Checked 2026-10-11.
• Figma MCP server introduction, Figma Developer Docs: the remote server connects to Figma's hosted endpoint without the desktop app, and Figma recommends it. Checked 2026-10-11.

Figma is a trademark of Figma, Inc. Canvashand is independent and not affiliated with Figma, Inc.