Your AI assistant can hit Figma’s daily limit halfway through a design review, with screens still to check and fixes still to make. Use a small tool to gather the layer details and screenshots from Figma. Give those to your assistant for the review, then ask it to make the edits in Figma. You’ll see what this saves on a design review and get setup instructions you can hand to a developer. The limits in this guide are from Figma’s documentation as of 20 November 2026. Figma can change them. See Figma’s MCP limits.
In short
- MCP is the connection your assistant uses to look at your Figma file and make edits. When it asks Figma for a frame’s layers or a screenshot, that request is called a call. How many you get depends on your Figma plan and seat.
- The REST API is another way for a tool to ask Figma for things like layer details and screenshots. In this guide, the tool uses a personal key that only lets it read the file. Those requests have their own limit.
- Get the layers and screenshots through the API. Then give your assistant all the edits for one Figma page in the same message.
Why the limit bites
Figma counts the requests your assistant makes to look at your file. With a Full or Dev seat on Professional or Organization, your assistant can make up to 200 requests a day to look at your files. It can make up to 10 a minute on Professional and 15 on Organization. With a Full or Dev seat on Enterprise, the daily limit is 600. View and Collab seats get up to 20 a month. On the Starter plan, Full and Dev seats have no MCP access; View and Collab seats get up to 20 a month. See Figma’s MCP limits by plan and seat.
Checking frames one by one uses up the allowance quickly. For each frame it changes, your assistant might ask Figma for the layers, ask for a screenshot, then ask for another screenshot to see how the fix looks. A 40-screen review can use about half your daily allowance. The requests to watch are the ones your assistant makes to see what’s already in the file, including the screenshots it takes to check its edits.
Two ways to work with a Figma file
What you need to know
MCP
REST API
When you get layers and screenshots through the API, those requests use the API’s allowance. Your assistant still has its full MCP allowance available for work it does through that connection.
Get screenshots first, then ask for edits
Here’s how to split the review into three steps.
- Get the frames you want to review. Give the tool a list of Figma frames. It can ask for the layers of several frames together and do the same for their screenshots. See Figma’s instructions for requesting layers and images.
- Review the screenshots. Figma sends back a link for each screenshot it can make. You can open it yourself or share it with your assistant. Opening the link uses none of either Figma allowance.
- Ask your assistant to edit the file. In this setup, your assistant makes the edits through MCP. Put all the fixes for one page in the same message and ask your assistant to list the frames and layers it changed.
Figma says requests to look at your file count toward the limit and lists some tools that write to files as exempt. The example below shows the totals both ways because Figma’s list doesn’t name the editing tool used here. See Figma’s rules on what counts.
A worked example
Take a checkout review. The same 20 fixes use 1 of your 200 daily MCP requests for looking at the file, down from 101.
Imagine you’re reviewing a checkout flow with 40 screens across 4 Figma pages. You check the layers and a screenshot of every screen, make 20 fixes (5 per page), then check a fresh screenshot of each screen you fixed. All three approaches cover the same review and make the same fixes. The three blocks show how often each approach asks Figma to look at something or make a change.
For this example, you have a Full seat and can edit a sample file on a Professional team. Claude Code connects directly to Figma online. If you have a View or Collab seat, compare the totals with your monthly limit. The tool asks Figma for 10 screens at a time when it gathers layers or screenshots through the API. Each approach starts by asking Figma for a list of pages and screens. In the API approach, one set of screenshots comes through on the second try. Figma’s API can’t make a picture of one hidden frame, even when asked for that frame on its own. The example uses an MCP screenshot for that frame.
A. Screen by screen
- 101 requests to look
- 20 requests to edit
- 0 API requests
B. Page by page
- 65 requests to look
- 4 requests to edit
- 0 API requests
C. API for the review
- 1 request to look
- 4 requests to edit
- 13 API requests
Add the requests across both connections and the three approaches make 121, 69 and 18 requests, respectively. In C, you still check 60 pictures across the first review and the final checks. Opening the pictures Figma sends as links uses none of your allowance.
- A. Screen by screen. Your assistant asks for the list of pages and screens once, then for the layers of each of the 40 screens. It takes 40 screenshots before editing and 20 to check the fixes. It sends a separate request for each of the 20 fixes.
- B. Page by page. After the list of pages and screens, your assistant asks for the layers of each of the 4 pages at once. It still asks for each screenshot separately. It sends one request with all the fixes for each page.
- C. API for the review. The tool uses the API to list the pages and screens, then for the layers of each page, and then for the screenshots. Two of those requests are retries, one for the set that failed and one for the hidden frame. Your assistant uses MCP once to take the hidden frame’s screenshot and four times to make the edits, one per page.
Of the 200 daily MCP requests for looking at the file, A uses 101, B uses 65 and C uses 1. If every editing request in the example also counts, the totals are 121, 69 and 5. Asking for a whole page’s layers at once saves 36 requests from your MCP allowance. Getting the layers and most screenshots through the API saves another 64.
Same review, same fixes: 121 requests one screen at a time, 69 page by page, and 5 of your assistant’s allowance when the API does the looking.
These totals show how the requests would add up under Figma’s published limits. We haven’t run this review. The example asks for 10 screens at a time. Figma’s instructions show how to ask for several at once without giving a maximum. With a Full seat on Professional, Figma allows 15 requests a minute for the layers and screenshots used here. The example’s 13 API requests fit within that limit if you have the allowance available. See Figma’s API limits. If the tool says you’ve reached Figma’s limit, wait as long as Figma asks before trying again.
Create a key that can only read your file
A token is a key you create in Figma. The permission you choose here lets the tool see the layers and get screenshots from files you can already open. Setting it up takes a few minutes. You can share these instructions with the developer who sets up your team’s tools.
- In Figma, open Settings, then the Security tab, and choose Generate new token.
- Choose an expiry date soon after you’ll finish using the key. Select only
file_content:read, the setting that lets the tool see layers and get screenshots. See Figma’s token permissions. - Copy the key straight into your password manager. Figma shows it only once. Keep it out of AI chats, documents and shared code. See Figma’s instructions for personal access tokens.
- If you see that the key was used when you weren’t expecting it, disable it in Figma’s Security settings.
Figma uses the key to check which files you can open. The tool should send the key only to Figma.
For whoever sets this up
Send the token only to api.figma.com, in the X-Figma-Token header. Here is one request for several screens at once. The token comes from the environment, and the file key and screen ids are placeholders:
curl -s -H "X-Figma-Token: $FIGMA_TOKEN" \
"https://api.figma.com/v1/files/FILE_KEY/nodes?ids=1:2,1:3,1:4&depth=2"
And pictures for the same screens. A null for a screen means that picture failed:
curl -s -H "X-Figma-Token: $FIGMA_TOKEN" \
"https://api.figma.com/v1/images/FILE_KEY?ids=1:2,1:3,1:4&format=png&scale=1"
If Figma answers with a 429, wait the number of seconds in the Retry-After header, then retry.
Picture links expire after 30 days. Both requests are in the same rate-limit group. This guide covers reading file content only. The REST API can also change files, but that needs other permissions.
Ask for all the edits on one page
To make edits, your assistant needs to connect directly to Figma online, and you need permission to edit the file. See Figma’s guide to connecting your assistant. You’ll need a Full seat to edit files outside your own drafts. Figma says editing through your assistant is free while the feature is in beta. It plans to charge based on how much you use it. See Figma’s guide to editing through MCP.
Send your assistant one message with all the fixes for a page. Refer to screens by their names in Figma.
On the Checkout page, make these 5 fixes.
1. Change the main button label to "Pay now" on the Cart and Payment screens.
2. Right-align the price on the Order summary screen.
3. Rename the "Delivery" heading to "Shipping" on the Shipping address screen.
4. Change "Edit" to "Edit address" on the Review order screen.
5. Change the confirmation heading to "Order placed" on the Confirmation screen.
When you're done, tell me which screens and layers you edited and what each looked like or said before and after.
Five fixes on each of four pages: four requests instead of twenty. Use the assistant’s list of changed layers to get fresh screenshots of just those frames through the API.
What this setup can access
- Variables. Figma requires Enterprise to read your file’s variables through the API. On other plans, ask your assistant to look them up through MCP. That uses part of your MCP allowance. See Figma’s API permissions.
- Which files you can open. Your key only works with files you already have permission to view.
- Making edits. The key in this guide is for looking at the file. Ask your assistant to make the edits through MCP.
If your team is on Enterprise, check Figma’s API limits by plan before using the example’s numbers.
Sources
- MCP server: rate limits and access
- MCP server: tools
- MCP server: introduction and clients
- REST API: rate limits
- REST API: file endpoints
- REST API: scopes
- REST API: personal access tokens
On your next review, see how often your assistant asks Figma for layers or screenshots. Try getting those through the API, then give your assistant the fixes one page at a time.
AI TOOLS
Want your design team to get more from Figma and AI?
We can set up your Figma and assistant workflow, so reads, drawing and review run smoothly.