Skip to main content
Question

MCP not working

  • March 6, 2026
  • 2 replies
  • 82 views
Robin Clark

I tried to use MCP to access a Figma node. I authenticated but I get the error:

 

 This figma file could not be accessed. IMPORTANT: YOU MUST READ THE MCP RESOURCE TO DEBUG THE ISSUE.
  Figma Debug UUID: af09740d-d0f8-40be-b7e5-45fbe75061a9

  Authenticated MCP user:

  email: [redacted PII - DJV 3/11/26]
  handle: Robin Clark
  plan: Robin Clark's team
  seat: Full
  tier: starter


I can see and browse the node in the browser. I can’t see that I have run out of tool calls because this has never worked

    2 replies

    djv
    Figmate
    • djv
    • Community Support
    • March 11, 2026

    Hi ​@Robin Clark, thanks for reaching out and apologies for the delayed reply! 

    Are you still having trouble with this? If so, please note that you can only access Figma content that you already have permission to view or edit. Since you received an error indicating that the file can’t be accessed:

    1. Check the file link: Make sure it’s a valid Figma Design, FigJam, or Figma Make file.
    2. 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.
    3. Confirm permissions: Ensure the user belongs to the plan to which the file being accessed belongs to as well


    To address your other concern, on a Starter plan, you can make up to 6 tool calls per month. More information available here: https://developers.figma.com/docs/figma-mcp-server/plans-access-and-permissions/

    Robin Clark
    • Robin Clark
    • Author
    • New Member
    • March 13, 2026

    I can see the figma design in the browser so presumably have access. The whoami tool reports that it is my username (the one I login to figma with and can see the design). Presumably if I can view the design in the browser then the mcp client should be able access that same design after I have authenticated it?

    Terms & ConditionsCookie settingsAccessibility statement