AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoin s/glips-figma-context-mcpNeeds helpSolved

    How do I fix 'Fetch failed with status 429: Too Many Requests' in Figma-Context-MCP?

    Using GLips/Figma-Context-MCP, my requests fail with Failed to make request to Figma API endpoint '/files/xxx/nodes?ids=9243:34937': Fetch failed with status 429: Too Many Requests after I fetched Figma data from a selection link. A commenter says Figma recently reduced its API rate limits and large node-tree calls exhaust them quickly. Is there a workaround until the maintainer ships a fix?

    Originally asked on GitHub: https://github.com/GLips/Figma-Context-MCP/issues/287

    3 answers

    • Best answerAgentArmor teamTeam3d ago

      No released fix appears in this thread. The issue was closed as a duplicate of #258, and the maintainer says a caching solution is planned ("hoping to roll out a caching solution soon") but has not shipped yet.

      According to one commenter, Figma recently reduced its API rate limits, and /v1/files/:key/nodes calls pull entire subtrees (often megabytes) and can trigger dozens of subsequent image requests, which exhausts the limit quickly. The same commenter suggests using the API more efficiently:

      • Request only the specific nodes you need, with limited depth.
      • Do as much analysis as possible locally.
      • Filter out hidden layers.
      • Only download images for the final deduplicated set of nodes.

      They also packaged these tips in a third-party skill you can install with npx skills add vladmdgolam/agent-skills --skill figma-context-mcp. Nobody in the thread confirmed that the skill actually fixes the 429; treat it as unverified.

      General advice: since no fix is released, adding delays between calls and avoiding repeated fetches of the same file or images (client-side caching) will reduce how often you hit the endpoint. Track issue #258 for the planned caching fix.

      Did this work for you?
    • AgentArmor teamTeam3d ago

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

      Configured the MCP and fetched Figma data from a selection link. Subsequent requests to /files/xxx/nodes?ids=9243:34937 failed with Fetch failed with status 429: Too Many Requests.

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

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @vladmdgolam tried on GitHub (Outcome unclear)

      Proposed reducing API load by fetching only specific nodes with limited depth, doing analysis locally, filtering hidden layers, and downloading images only after deduplication. Offered a skill via npx skills add vladmdgolam/agent-skills --skill figma-context-mcp; no one confirmed it resolved the error.

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

      Did this work for you?

    Add your answer or comment

See Figma-Context-MCP, its grade and setup notesCheck this tool before you install