I have a Figma Pro Plan, and now Claude is telling me that, “Figma puts a cap on how many MCP requests can be made in a given window. When that cap is hit, every call returns that error until it resets.”
Where is this cap documented? How can I tell when it will reset? Why didn’t it mention “caps” when I paid for this membership? This is holding up development now, and actually as a STOCK HOLDER in this company, I am not happpy about this at all.
By the way, in looking at the capped allowances, for a PRO plan it says per minute and per day, but I haven’t used this at all today. So why am I being capped? Is it truly my membership level? https://developers.figma.com/docs/figma-mcp-server/rate-limits-access/
I have a Figma Pro Plan, and now Claude is telling me that, “Figma puts a cap on how many MCP requests can be made in a given window. When that cap is hit, every call returns that error until it resets.”
Where is this cap documented? How can I tell when it will reset? Why didn’t it mention “caps” when I paid for this membership? This is holding up development now, and actually as a STOCK HOLDER in this company, I am not happpy about this at all.
You’re most likely hitting either a shared MCP server rate limit or a token/session-level throttle, not necessarily your entire Figma Pro account limit directly. The confusing part is that the limits documented for the Figma MCP server don’t always clearly explain how Claude aggregates requests behind the scenes, especially when multiple background retries or large context pulls happen automatically.
A few things worth checking:
• Disconnect and reconnect the Figma MCP integration completely inside Claude/Desktop. Sometimes stale sessions continue counting failed retries against the limit.
• Generate a fresh Figma access token and reconnect the MCP server. Old or partially expired tokens can trigger misleading “cap reached” responses.
• Check whether Claude is repeatedly polling large files/components in the background. Even a few prompts can create dozens of MCP calls if the design system is large.
• Try testing with a smaller Figma file/project to confirm whether the issue is request volume vs authentication/session related.
• Wait 30–60 minutes and retry. In many cases the MCP limits are rolling-window based rather than true daily resets, which is why you can still get capped even if you barely used it “today.”
• If possible, inspect the MCP logs or Claude console output. Sometimes the actual API error from Figma contains more detail than Claude surfaces in the UI.
Honestly, Figma should document this much more clearly because the current wording makes it sound like the limits are only tied to membership tier usage, when there may also be backend infrastructure throttles or hidden burst limits involved.
You may also want to open a direct support ticket with Figma including:
your plan type
approximate request count
timestamp of the issue
whether the file is especially large
the exact MCP error response
That usually gets escalated faster than community posts alone.
Thanks for your reply. All I get now is “Unable to connect to extension server. Please try disabling and re-enabling the extension.” and no matter how many times I do this, it’s the same message.
That new error "Unable to connect to extension server" is actually a separate problem from the original rate limit. The good news is it's fixable. Let me walk you through what's actually happening and the steps that have worked for others in the same situation.
WHAT'S REALLY GOING ON
This error typically means one of three things:
1. The Figma Desktop MCP server (which runs locally on port 3845) has lost its session and can't reconnect cleanly.
2. There's a protocol version mismatch between your Claude client and the Figma extension — this became a widespread issue after a Claude Desktop update in April 2026 that bumped the MCP protocol version to 2025-11-25, while the Figma extension still responds with 2025-06-18.
3. You may have both a "Figma Desktop" connector AND a "Figma (remote)" connector installed at the same time, causing a conflict that breaks both.
Simply toggling the extension on/off doesn't fix any of these, it just restarts a broken session.
STEP-BY-STEP FIX (try in order)
Step 1 — Check for duplicate connectors
Go to your Claude settings → Connectors. If you see two Figma-related entries (one for desktop/local and one for remote/cloud), remove BOTH of them completely. Then reinstall only the one you actually need. This conflict alone breaks the connection entirely and is the #1 cause of this exact error right now.
Step 2 — Full quit and restart Figma Desktop
Don't just close the window. Fully quit the Figma desktop app (Cmd+Q on Mac / right-click tray icon on Windows → Quit). Then reopen it, open your file, go to Dev Mode, and make sure the MCP server is toggled ON before reconnecting Claude. The MCP server only runs when a file is actively open in the desktop app it won't work from the browser.
Step 3 — Remove and re-add the connector with a fresh token
In Claude settings, remove the Figma connector entirely. Then go to Figma → Account Settings → Personal Access Tokens → generate a brand new token. Re-add the connector using this fresh token. Expired or partially broken tokens silently cause this error.
Step 4 — Check your MCP URL endpoint
If you're configuring the MCP server manually, make sure you're using:
http://127.0.0.1:3845/mcp
...NOT the old /sse endpoint. The /sse path is deprecated. Some users found that switching to /mcp fixed their connection immediately.
Step 5 — Windows-specific: Check if port 3845 is already occupied
If you're on Windows, another process or a leftover port proxy rule may have already claimed port 3845 before Figma can start its MCP server. Open PowerShell as Administrator and run:
netsh interface portproxy show all
If you see a rule for port 3845, delete it with:
netsh interface portproxy delete v4tov4 listenport=3845 listenaddress=0.0.0.0
Then restart Figma Desktop.
Step 6 — Check for a Claude Desktop update
If you're on Claude Desktop and haven't updated recently, do it now. The April 2026 update introduced a protocol version that the older Figma extension wasn't fully handling some users saw the connection completely drop after this. Updating Claude Desktop and restarting fixed it for several people.
IF NOTHING ABOVE WORKS
This is most likely a temporary backend issue on Figma's MCP infrastructure. It has happened before and Figma's engineering team has resolved it within hours each time. At this point, your best move is:
- Open a direct support ticket at figma.com/support and include: your Pro plan details, the exact error message, your OS, and the timestamp it started.
- Reference this thread so they can see the history.
Support tickets with plan type + timestamp get escalated faster than community posts.
Hope one of these resolves it for you. Let me know which step you're on and your OS (Mac or Windows) and I can explain better.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.