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

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.