Figma MCP fails on prototype URL: 'Cannot read properties of null (reading components)'

5 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Fixed: the maintainer closed the issue and pointed to PR #344 as the fix (April 2026). The thread does not name a release version, and no user confirmed the fix, so update the figma-developer-mcp package to a version that includes PR #344 and retest.

  What happened: get_figma_data accepts the same fileKey and nodeId that a prototype URL contains, but the API result for this file came back null where the tool expected a components property, so it crashed with 'Cannot read properties of null (reading components)'. Calling get_figma_data without nodeId produced 'Failed to make request to Figma API: Fetch failed with status 400: Bad Request'.

  Before the fix, the maintainer asked whether the personal access token had read access to the file behind the prototype. The reporter confirmed the token had full read access to the project and asked whether being inside a Figma branch could be the cause; the thread never confirms that the branch was the culprit.

  General advice: after updating the package, restart Claude Code so the MCP server process is reloaded, then retry get_figma_data with the prototype URL. If the error persists, verify that the token can read the specific branch or version of the file, not just the parent project. Keep the Figma token scoped as read-only and avoid pasting it into prompts or logs.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Didn't work)

  Reporter called get_figma_data with the fileKey and nodeId taken from a prototype URL; the tool failed with 'Cannot read properties of null (reading components)'.

  Source: https://github.com/GLips/Figma-Context-MCP/issues/201 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Didn't work)

  Reporter then called get_figma_data with only the fileKey and no nodeId; the Figma API returned 'Fetch failed with status 400: Bad Request'.

  Source: https://github.com/GLips/Figma-Context-MCP/issues/201 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @ihardyslide tried on GitHub (Outcome unclear)

  Reporter confirmed the personal access token had full read access to the project containing the prototype and asked whether being inside a Figma branch caused the issue; no reply in the thread confirms this.

  Source: https://github.com/GLips/Figma-Context-MCP/issues/201#issuecomment-3112632922 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @GLips tried on GitHub (Outcome unclear)

  Maintainer announced the issue was fixed in PR #344 and asked the reporter to confirm; no confirmation appears in the thread.

  Source: https://github.com/GLips/Figma-Context-MCP/issues/201#issuecomment-4340941166 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport