● plugin:figma:figma - whoami (MCP)
⎿ {
"handle": "...",
"email": "redacted",
"plans": [
{
"name": "redacted",
"seat": "View",
"tier": "starter",
"key": "team::1597224330267628660",
"seat_type": "view"
},
{
"name": "redacted",
"seat": "Dev",
"tier": "pro",
"key": "team::1238208331265141733",
"seat_type": "developer"
}
]
}
⎿ [Resource link: rate-limits-access.md] file://figma/docs/rate-limits-access.md
03:54 PM claude-opus-4-8
● Authenticated as ... Now let me try to access the specific file.
● plugin:figma:figma - get_metadata (MCP)(fileKey: "OkMuoAjqzzcfHO0HsV7KAD", nodeId: "22-552", clientFrameworks: "react", clientLanguages:
"typescript")
03:54 PM claude-opus-4-8
● Let me read the debug resource to understand the access issue.
● readMcpResource(Read resource "file://figma/docs/rate-limits-access.md" from server "plugin:figma:figma")
⎿ {
"contents": [
{
"uri": "file://figma/docs/rate-limits-access.md",
"mimeType": "text/markdown",
"text": "# Rate limits & access\n\n## Who can access the MCP server?\n\nAccess to the Figma MCP server depends on your Figma plan
and seat type. Per-minute rate limits apply in addition to daily or monthly tool call limits.\n\n<table id=\"rate-limits-tier-table\"
class=\"tier-table\">\n <thead>\n <tr>\n <th>Seat</th>\n <th>Starter</th>\n <th>Professional</th>\n
<th>Organization</th>\n <th>Enterprise</th>\n </tr>\n </thead>\n <tbody>\n <tr class=\"tier-group-1
tier-first-row\">\n <td class=\"seat-col\">View, Collab</td>\n <td rowspan=\"2\">Up to 6/month</td>\n <td>Up
to 6/month</td>\n <td>Up to 6/month</td>\n <td>Up to 6/month</td>\n </tr>\n <tr class=\"tier-group-1
tier-last-row\">\n <td class=\"seat-col\">Dev, Full</td>\n <td>Up to 200/day<br />10/min</td>\n <td>Up to
200/day<br />15/min</td>\n <td>Up to 600/day<br />20/min</td>\n </tr>\n </tbody>\n</table>\n\nRate limits apply to Figma
MCP server tools that read data from Figma. Some tools, such as those that write to Figma files, are exempt from the rate limits. Exempt
tools include:\n\n- `add_code_connect_map`\n- `generate_figma_design`\n- `whoami`\n\nFigma reserves the right to change rate
limits.\n\n## What if I'm rate-limited?\n\nIf you're encountering rate limits with the Figma MCP server, you can increase your limits in
certain scenarios by upgrading your seat or plan.\n\n- If you're on a Starter plan (6 tool calls per month), upgrade to a Pro,
Organization, or Enterprise plan. Ensure you have a Full or Dev seat on the new plan.\n\n- If you have a View or Collab seat on an
Organization or Enterprise plan (6 tool calls per month), upgrade to a Full or Dev seat.\n\n- If you have a Full or Dev seat on an
Organization plan (200 tool calls per day), upgrade to an Enterprise plan (600 tool calls per day).\n\nFull and Dev seats on Enterprise
plans get the least-limited usage, as described in [Who can access the MCP server?](#who-can-access-the-mcp-server)\n\n## Which MCP
clients are supported?\n\nTo use the MCP server, you’ll need a code editor or application that supports MCP servers (for example, VS
Code, Cursor, or Claude Code).\n\nOnly clients listed in the [Figma MCP Catalog](https://www.figma.com/mcp-catalog/) are able to connect
to the Figma MCP Server. If you’re a developer interested in connecting a new MCP client, you can [join the
waitlist](https://form.asana.com/?k=kBG-ejRQTdY8x_H6a4vM3Q&d=10497086658021).\n\n## Why am I getting permission errors?\n\nYou can only
access Figma content that you already have permission to view or edit. If you get an error indicating that resources can’t be
accessed:\n\n1. **Check the file link:** Make sure it’s a valid Figma Design, FigJam, or Figma Make file.\n2. **Verify your user:** Run
the whoami tool to confirm the email used for authentication. It also tells you all the plans the user belongs to and their seat types in
these plans.\n3. **Confirm permissions:** Ensure the user belongs to the plan to which the file being accessed belongs to as well\n"
}
]
}
03:54 PM claude-opus-4-8
● No — I can't access that Figma file.
What I confirmed:
- ✅ Authentication works. I'm connected to the Figma MCP server as ....
- ❌ The file ... (OkMuoAjqzzcfHO0HsV7KAD node ...) returns an access error.
Why this is happening:
You have two plans on this account:
┌─────────────┬─────────┬──────┬───────────────┐
│ Plan │ Tier │ Seat │ MCP limit │
├─────────────┼─────────┼──────┼───────────────┤
│ redacted │ Starter │ View │ 6 calls/month │
├─────────────┼─────────┼──────┼───────────────┤
│ redacted │ Pro │ Dev │ 200/day │
└─────────────┴─────────┴──────┴───────────────┘
The MCP server only lets you read files you already have permission to view/edit. The most likely causes are:
1. No view/edit permission — your account isn't a member of the project/team that owns ... , so the file simply isn't visible to you. (This is
the most common cause of this exact error.)
2. Seat/plan limits — if ... lives under "..." (Starter + View seat), that seat is capped at 6 MCP tool calls/month and may have been
exhausted, or View seats may not have dev-mode read access there.
To get access, please:
- Confirm the file is shared with ... (open it in your browser while logged in as that account), and/or
- Make sure it lives under a plan where you hold a Dev/Full seat (your "..." Pro plan), since the View seat on the Starter plan is heavily
limited.
Once it's shared/accessible to that account, I can pull the design context, screenshots, or metadata for node ... . Want me to retry after
you've checked the sharing settings?
✻ Cooked for 37s
❯ which error are you getting? show me exactly
● Here's the exact error returned by the get_metadata tool call:
This figma file could not be accessed. IMPORTANT: YOU MUST READ THE MCP RESOURCE TO DEBUG THE ISSUE.
[Resource link: rate-limits-access.md] file://figma/docs/rate-limits-access.md
Figma Debug UUID: 98dfb772-fd5e-44c3-9411-3ff9a52d61a3
That was wrapped in an <error> tag, so the call failed outright (not a partial/empty result).
The call I made was:
- Tool: get_metadata
- fileKey: OkMuoAjqzzcfHO0HsV7KAD
- nodeId: ....
The message is generic — it doesn't say whether it's a permissions issue or a rate-limit issue, just "could not be accessed" plus the debug UUID.
Want me to retry the same call, or try a different tool (e.g. get_screenshot / get_design_context) on the same node to see if it returns a more
specific error?
Hi there,
I’m trying to use claude code to pull out designs to our frontend. I have a dev seat on the team that owns the file. Claude for some reason says the error is ambiguous and cannot say whether it is a rate limit error or access control issue. It worked just fine this morning, however I am very very doubtful I already did 200 tool calls in just a few minutes. I also just double checked the tool calls I’ve done and I could count them on one hand.
Anyone could help me by any chance?