Figma MCP limit reached: what it means and what you can do
You see this when your account has used up the number of calls Figma allows its MCP server to answer for your seat. The allowance resets on a schedule that depends on your seat, and it applies to the read tools your agent uses to look at your design. As of November 9, 2026, a View or Collab seat gets 20 calls per month on every plan.
The published limits
| Seat and plan | Limit |
|---|---|
| View or Collab seat, any plan | 20 calls per month |
| Starter plan, Full or Dev seat | Not available; Starter has no Full or Dev seat |
| Pro, Full or Dev seat | 200 per day, 10 per minute |
| Organization | 200 per day, 15 per minute |
| Enterprise | 600 per day, 20 per minute |
Source: Figma developer docs, MCP server rate limits and access, checked November 9, 2026. Limits may change. Figma’s page is the authority.
Why agents hit it quickly
An agent that explores a design before editing it can make many read calls for one task: one for the page, others for frames, text and styles. At 10 calls a minute, a single exploratory prompt can use the minute’s allowance. At 20 a month, a View seat covers very little.
Your options
- Wait for the reset. Free, and fine for occasional use.
- Use a seat with a higher allowance. That is a Figma plan decision. Compare the table above with what you pay.
- Ask for fewer, narrower reads. Point the agent at one frame instead of a whole file.
- Use a local option. FigmaMCP reads and edits through the Plugin API of the Figma desktop app on your Mac. It never calls Figma’s MCP server, so these call limits are not part of how it works.
What the local option asks of you
Install with:
npx figmamcp setup
FigmaMCP is independent software. Your use of the Figma desktop app remains subject to Figma’s terms.
