Skip to main content
Question

MCP limit education plan

  • June 30, 2026
  • 1 reply
  • 80 views
Roaa Mohamed

Hi — I'm on a Student/Education plan (Full seat) and I'm hitting a rate limit on the Figma MCP server (Dev Mode plugin API) where figma.loadFontAsync() calls hang indefinitely and never resolve, even after fully quitting and restarting the Figma desktop app. Sync operations (creating shapes, no font loading) still work fine, so this is specific to the MCP tool-call quota, not a general outage.

Your rate-limits documentation (developers.figma.com/docs/figma-mcp-server/rate-limits-access/) lists quotas for Starter (6 calls/month), Organization Full/Dev seats (200 calls/day), and Enterprise (600 calls/day) — but doesn't mention Education/Student plans at all.

Could you tell me:

  1. What MCP tool-call quota applies to a Student plan Full seat?
  2. Is the reset window daily, monthly, or something else?
  3. When will my limit reset?


Good question to ask — and honestly, this is important: we never received an explicit rate-limit error message. Every single call — including the ones that failed — returned the exact same generic response:

Code executed with no return value.

That's the normal/expected response format for any async code in this tool, whether it succeeds or fails. There was no error text, no "rate limited," no HTTP 429, no exception thrown — loadFontAsync() just silently never resolves, and the changes never persist when we check afterward.

The only actual error message we saw all session was unrelated to fonts — a stale node reference:

Error: in remove: The node with id "2076:77" does not exist

That was just from trying to remove a frame that no longer existed, not a rate-limit symptom.

This actually matters for your message to Figma — worth telling them explicitly:

There's no visible rate-limit error returned — figma.loadFontAsync() calls simply hang/never resolve, with no exception or error message. I only inferred this might be a rate limit because (a) sync operations still work fine, (b) it persisted across a full app restart, and (c) per Figma's MCP rate-limit docs, hitting a quota is the only documented scenario that would cause font-loading calls to specifically fail.

That's more accurate than claiming you saw a rate-limit message — because we didn't. It might prompt them to look for a different cause (e.g., a stuck plugin session, a bug, or genuinely a silent quota block with no surfaced error).

 

1 reply

Celyn_L
Figmate
  • Celyn_L
  • Figmate
  • July 1, 2026

Hi ​@Roaa Mohamed, Celyn from Figma Community Support here.

Thanks for reaching out and for sharing all these context. Happy to help!

The Figma MCP Server daily rate limits for Education plan users have now been increased to match Professional plan limits: https://developers.figma.com/docs/figma-mcp-server/rate-limits-access/

That means your current limits are:

  • 200 tool calls per day (quota resets daily)
  • 10 tool calls per minute for Dev/Full seats

Based on your description though, it doesn't clearly sound like a rate-limit issue. The fact that figma.loadFontAsync() hangs without returning an explicit rate-limit error, while other operations continue to work, suggests there may be something else going on.

To help us investigate further, I've gone ahead and created a support ticket for you (#1991631). When you get a chance, please reply directly to the ticket with:

  • Which AI coding client you're using (Cursor, Claude Code, VS Code, etc.).
  • Whether this happens across all Figma files or only a specific one.
  • Any MCP logs you can share.
  • A short screen recording showing the behavior, if possible.

Our team will take a closer look from there. Thanks! 

Terms & ConditionsAccessibility statement