Skip to main content
Question

MCP get_metadata/get_design_context fails with "don't have edit access" despite owner + edit permissions (multiple debug UUIDs)

  • September 1, 2026
  • 1 reply
  • 5 views
Kelson da Costa Medeiros

I'm hitting a persistent access error using the Figma MCP integration (Claude Code / Claude Desktop's plugin:figma:figma connector) against my own file.

Account: (redacted by the moderator due to PII) ("Kelson da Costa Medeiros"), team "Kelson da Costa Medeiros's team" (starter tier, seat shows as "Full" via whoami but I purchased a Dev seat).

File: https://www.figma.com/design/lLmb3BJsEXJ4FGJjwfIkk8/Sabi%C3%A1 — I am the owner of this file. The Share dialog confirms "Anyone in Kelson Medeiros" has can edit, and I (owner) obviously have edit access.

Error: Every call to get_metadata (and presumably get_design_context) returns:

"Looks like you don't have edit access to this file. The file owner can share it with you and make you an editor."

What I've tried (no change, same error each time):

  1. Verified file sharing permissions (already correct — owner + team-wide edit access).
  2. Fully disconnected and reconnected the Figma MCP integration from Claude Code (/mcp disconnect + reconnect).
  3. Restarted the Claude Desktop app after reconnecting.
  4. whoami succeeds every time and correctly returns my account.

Debug UUIDs collected across attempts (all same error, different UUID each time — similar pattern to a thread I found: "Figma MCP in Claude: File access broken, multiple debug UUIDs"):

  • a70a8b94-14dc-4e76-9972-8b82fe92641d
  • 8d2ca983-cd14-497e-9ae1-71642985f911
  • 78f9e008-3321-4814-ae28-fe553f8513c1
  • 6acdb7be-5ada-4e71-8c65-43a4d6cbdd1f
  • eb79f223-1bb6-459a-9133-9bedfb87ea91

Could someone take a look? This is blocking a design-to-code workflow.

1 reply

Tom Reem
Figmate
  • Tom Reem
  • Figmate
  • September 1, 2026

Hi ​@Kelson da Costa Medeiros — welcome to Figma Forum, and thanks for the thorough writeup.

To narrow this down a bit more, could you check on these three things and let me know? Please don't paste your full whoami output — just the fields below.

  1. In your plans array: How many entries, and the tier and seat for each? Along with this, is the plan where you purchased the Dev seat one of them?
  2. Is the file you're calling get_metadata on stored in that plan with the Dev seat, or in the Starter team?
  3. Run create_new_file, then call get_metadata on that new file. Does it fail too? If it does, please share the debug UUID from that call along with the timestamp — a failure on a file you just created helps us zero in.

Our MCP server FAQs note that Dev seats have read access to metadata and design context outside of drafts, so what you're seeing doesn't line up with expected behavior, which is why I'd like to pin down the details above.

Once I have these, I'll relay everything to our Technical Quality team for a deeper dive.

Terms & ConditionsAccessibility statement