Figma-Context-MCP in Cursor returns 429 Too Many Requests even though curl works?

6 answers

• Best answerAgentArmor teamTeam3d ago

  The issue is still open as of late November 2025, but the cause is explained: the MCP server has no built-in rate limiting; the 429s come from Figma's REST API. Figma introduced new rate limits on Nov 17: free accounts get 6 requests per month, and paid/dev-seat accounts get up to 10 requests per minute for Tier 1 endpoints (get file and get image, both used by Framelink). Direct curl succeeding doesn't rule this out; you may have had capacity at that moment. The maintainer asked for the 429 response headers (Retry-After, X-Figma-Plan-Tier, X-Figma-Rate-Limit-Type, X-Figma-Upgrade-Link) to diagnose the rate-limit type; one reporter couldn't see the headers even after prompting the LLM to return them. General advice: inspect the raw MCP tool response rather than asking the LLM to summarize headers. A commenter found that if the project belongs to a workspace on the Starter plan, that plan's limits apply to you even if you have a paid seat; duplicating the project into your own paid workspace made their Professional plan limits apply and the 429 stopped. Another commenter reported the Dev Mode plan worked for them, though some users still hit 429 after upgrading; the maintainer suspects a delay in Figma applying the higher tier to the key.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @tkrzhkv tried on GitHub (Worked)

  After upgrading, rate limits persisted until the user duplicated the project into their own Professional workspace. The original project belonged to a Starter-plan workspace, whose limits applied to them. Once copied, their own plan limits applied and the 429 stopped.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @lucasmonstrox tried on GitHub (Worked)

  A commenter confirmed that choosing the Dev Mode plan worked for them ('it works for me').

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

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

  The reporter tried direct curl requests to Figma's API with the same API key; those succeeded but the MCP still returned 429.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @lucasmonstrox tried on GitHub (Didn't work)

  A commenter upgraded to Dev Mode after Figma's Nov 17 rate limit changes, but errors persisted.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @lucasmonstrox tried on GitHub (Didn't work)

  Another user upgraded to the dev version but still received the 'You've hit your rate limit' error after stepping away from the keyboard and returning.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport