Six tool calls a month is not a workflow

Figma’s MCP server reaches into your files through Figma’s own API, and that access is metered by seat. On a Starter plan, or with a View or Collab seat on a paid plan, Figma’s docs put you at roughly six tool calls a month. One real design-to-code session spends that before it has finished looking around.

So the error is not a bug, and waiting does not clear it. The path Figma points at is a Dev or Full seat on a paid plan, which is a reasonable ask if your team already pays for Figma and a hard stop if it does not.

There is a second version of this that catches people who have paid: the limit follows the team that owns the file, not your account. A file sitting in Drafts, or in a team still on Starter, gets Starter limits while whoami cheerfully reports that you are on pro.

Flaude sidesteps the whole mechanism. It is a plugin, so it works on the document open in front of you through the plugin API. No REST call, no seat check, no quota to spend.

Figma’s server is built to get design data out of Figma so an agent can write code from it. Point it at a finished frame and it will hand Claude the variables, the components and, with Code Connect, your actual component names. For engineers implementing a design that already exists, it is the best tool for that job and nothing here changes that.

Flaude goes the other way. It puts design into Figma: Claude reads your selection and then creates, restyles, renames and rebuilds real layers on the canvas. Frames, auto layout, text you can retype.

Which means the honest answer to “which one should I use” is often both, at different ends of the same week.