Skip to main content
Question

Figma MCP server stuck on Starter limits despite active Professional Dev seat

  • June 16, 2026
  • 1 reply
  • 7 views
Felipe Augusto

Hi everyone,

I'm hitting a backend sync issue with the Figma MCP server and I'd appreciate input from Figma staff or anyone who's seen this before.

The problem

I upgraded my team from Starter to Professional plan and assigned myself a Dev seat about 24 hours ago. Billing went through and the renewal date is correctly showing July 15, 2026 in my admin panel.

However, every MCP call still returns this error:

 

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

Upgrade your plan for more tool calls.

This contradicts what my own whoami MCP call returns:

 

{

"handle": "Felipe Augusto",

"email": "felipeaugustodev1@gmail.com",

"plans": [

{

"name": "A equipe de Felipe Oliveira",

"seat": "Dev",

"tier": "pro",

"key": "team::1648368301520545449",

"seat_type": "developer"

}

]

}

So whoami correctly identifies me as tier: "pro" with a Dev seat — but the rate limiter is still applying Starter limits (up to 6/month, per the rate limits doc).

Expected behavior per docs: 200 calls/day, 15/min on a Professional Dev seat.

What I've tried

  1. Disconnecting and re-authenticating the MCP server in my client (Claude).
  2. Waiting more than 12 hours for any async propagation.
  3. Submitted a support ticket via the "Contact us" form — no reply yet.

Question

Has anyone else seen the MCP tier cache get stuck after an upgrade? Is there a way to force-refresh the backend's view of my plan, or do I just wait on support? Any tips appreciated.

Thanks.

1 reply

Jaycee Lewis
Figmate

Hey hey ​@Felipe Augusto 🙌 The gap between your whoami (correctly showing tier: pro, seat: Dev) and the "Starter plan" error is a good clue.This could be a file-location issue rather than a stuck seat.

MCP rate 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 globally, but if the file your client is pointed at lives in your Drafts or in a team that's still on Starter, every read call gets the six per month Starter cap. even though whoami says pro. A teammate replied on a very similar case here

Quick way to confirm:

  • In one session, run whoami (you've already got pro/Dev), then make a read call—get_code or get_screenshot—against a node in a file you've verified is stored inside your Professional plan team ("A equipe de Felipe Oliveira"), not Drafts or an imported .fig. Check the file's location in the file browser to be sure.

  • If that call succeeds, it likely the file-location issue. For files sitting in Drafts or Starter, save a local copy and re-import it into the Professional plan team. Higher limits will apply once it's moved – What if I'm rate limited — Help center

  • If it still errors "Starter plan" on a file you've confirmed is in your Professional plan team, that's where we can head to support (I’m happy to help with that)

Let me know what file or team the failing call targets and we can take it from there. Thanks for the additional details! — Jaycee

Terms & ConditionsAccessibility statement