Figma MCP in Claude: File access broken, multiple debug UUIDs

● 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?

This figma file could not be accessed。

The Figma MCP indicates that the currently authenticated account does not have access to this file.

whoami result：
Figma handle:CodePencil
mail:jiawei.wang2021@gmail.com
plan:nbqushikeji's team
seat:Dev
套餐:pro

What's going on? I could access the design draft normally yesterday, but now it's not working

This is a log：

{

  "timestamp": "2026-06-03T11:24:22.750721",

  "request": {

    "method": "tools/call",

    "params": {

      "name": "get_design_context",

      "arguments": {

        "fileKey": "MENNuQ6ooGRArAeZokQQX4",

        "nodeId": "0:1",

        "excludeScreenshot": true,

        "forceCode": true,

        "disableCodeConnect": false,

        "clientLanguages": "dart",

        "clientFrameworks": "flutter"

      }

    }

  },

  "response": {

    "jsonrpc": "2.0",

    "result": {

      "isError": true,

      "content": [

        {

          "type": "text",

          "text": "This figma file could not be accessed. IMPORTANT: YOU MUST READ THE MCP RESOURCE TO DEBUG THE ISSUE."

        },

        {

          "type": "resource_link",

          "uri": "file://figma/docs/rate-limits-access.md",

          "name": "rate-limits-access.md",

          "mimeType": "text/plain"

        },

        {

          "type": "text",

          "text": "Figma Debug UUID: 486c92a2-b1b2-4acf-8aa3-2a8c57093530"

        }

      ],

      "_meta": {

        "mcpRequestId": "486c92a2-b1b2-4acf-8aa3-2a8c57093530"

      }

    },

    "id": 2

  }

}

Same problem

i’ve similar problem, happens today. It was accepting write request yesterday, any solution?

Once you have the editing permissions, you can read the file normally. I just tried it.
 

Once you have the editing permissions, you can read the file normally. I just tried it.
 

 

What is editing permission?

我也是 设计的codex也连不上 估计是figma有问题

The same problem, is it a bug of figma?

I am having the same issue 😥

Desktop MCP is ok

I have the same issue, but the MCP was working fine a few days ago.

Same problem here! Maybe is a Figma issue? 

Once you have the editing permissions, you can read the file normally. I just tried it.
 

 

What is editing permission?

dev seat does not have editing permissions.

Hey everyone, thanks for flagging this!

We're aware of this issue and our team is actively investigating. You don't need to take any action on your end and this isn't something a reconnect or re-auth will fix.

We'll update this thread as soon as we have more to share. Appreciate your patience while we work through it!

Hi ​@acud , Celine from Figma here! Our team is aware of the issue and is actively investigating it. I was able to see your support ticket on my end, and I've added a follow-up note internally for visibility.
 

Update: I've also noticed that a few other users in the Forum have reported similar behavior, so feel free to keep an eye on this thread for update.
(I've gone ahead and merged your topic into this thread to keep all updates and discussion in one place.)

Our entire team is currently unable to use Cursor to access the Figma MCP. This issue is blocking our workflow and affecting multiple team members. Please investigate and resolve it as soon as possible！！！

I’m using the remote Figma MCP server with Codex.  Authentication appears to work because whoami succeeds and shows that I have a Full seat on a student/education team. I am also the owner of the team/file. However, every attempt to read or write a Figma file fails with the same file access error.

whoami result, with private details redacted:

  {
    "handle": "REDACTED",
    "email": "REDACTED",
    "plans": [
      {
        "name": "REDACTED_TEAM",
        "seat": "Full",
        "tier": "student",
        "key": "REDACTED",
        "seat_type": "expert"
      }
    ]
  }

Response:
This figma file could not be accessed. IMPORTANT: YOU MUST READ THE MCP RESOURCE TO DEBUG THE ISSUE.

 Figma Debug UUID: c93ac4a9-6012-4f64-aab3-07788875d467

  Tool: mcp__figma.use_figma
  File key: REDACTED

  Response:
  ResourceLink(name='rate-limits-access.md', title=None, uri=AnyUrl('file://figma/docs/rate-limits-access.md'),
  description=None, mimeType='text/plain', size=None, icons=None, annotations=None, meta=None, annotations=None, meta=None)]

  Questions:

  1. Is remote Figma MCP read/write access supported for Full
     seats on student/education teams?

  2. If I am the owner of the team/file and whoami shows a Full
     seat, why would get_design_context, get_metadata,
     get_screenshot, and use_figma all return “This figma file
     could not be accessed”?

Hi Figma team,

I am reporting a Figma MCP Server issue.

What works:

• whoami works for steven9774@go.edu.tw
• - create_new_file works and creates new design files
• - generate_diagram works and creates a FigJam file

What fails:

• get_metadata fails with This figma file could not be accessed
• - use_figma fails with the same error
• - get_figjam fails with the same error
• - This also happens on newly created files immediately after create_new_file succeeds

Representative Debug UUID:

f94f9ad9-1e45-4d50-a5b5-02a886bf58a9

Recent Debug UUIDs:

0e2a9b46-6ae1-4f8e-8136-1e82f59576fe

daf12ee2-228d-420d-8a8c-f9159e047fad

238898ab-fbf3-413b-b4f3-67e6cf4181b6

Reproduction:

1. Connect Figma MCP through ChatGPT or Codex.
2. 2. Call whoami. It succeeds.
3. 3. Call create_new_file. It succeeds and returns a file key.
4. 4. Call get_metadata on that new file key. It fails.
5. 5. Call use_figma on the same new file key. It fails.

Expected:

The same account that can create a file should be able to read or edit it with MCP.

Could you check if this is a file context permission, rate limit, plan seat, or backend issue for this connector account?

Why did you even mark it as Solved? It’s not solved, it’s still occurring, your acknowledgment didn’t fix it.

also, https://status.figma.com/ should be updated with the issue?

just tried, it works for us now. Thanks!

Hey ​@Mikolaj Prus, I marked the reply as the best answer so anyone landing on this thread could quickly see we're actively investigating, not that the issue itself is resolved. I should've made that clearer.

And good shout on the status page, ​@p_sp. Because this was identified and fixed quickly, we didn't update it this time around.

We're still monitoring this, so if you're both still seeing the issue please do drop your details here, thanks! 

its fixed now, thanks figma team