Let Claude extend your flows

A copied screen is the starting point. The MCP connects Claude to your Figma file so it can read those layers and build on them — turning one screen into a whole app.

Runs on your existing Claude subscription. No API key to paste, no per-token bill, no Figma AI credits burned.

Get Pro, hosted MCPSelf-host it

What the MCP does

Talk to your canvas

Ask Claude to adjust a pasted screen in plain language, with no manual node wrangling.

Restyle and extend

Claude reads the copied layers, then recolors, relabels, and adds new screens that match.

One-URL setup with Pro

Pro hosts the MCP. Paste one URL into Claude and you are connected in about a minute.

Open source if you prefer

Rather run it yourself? Build the MCP locally and bring your own Claude API key. MIT licensed.

Use Claude in Figma as much as you want

It runs on the Claude subscription you already pay Anthropic for. No API key, no per-token bill. No Figma API rate limits, no Figma AI credits burned, no surprise lockouts. Here is the difference, with sources.

Talking to Claude through Figma's own API

The usual setup, and why it stalls.

  • Figma's REST API is rate-limited by plan and seat. For example, Tier 3 requests are about 10 per minute on the free Starter plan and 50 per minute on Pro.[1]
  • Go over and you get 429 errors. Designers report that just a handful of calls can trigger cooldowns of several days before access returns.[2]
  • Figma's own AI runs on monthly credits: 3,000 a month on a Professional Full seat, 500 for other seats, and they don't roll over.[3]

Talking to Claude through Flaude

The plugin over a WebSocket. No meter running.

  • Flaude connects through the Figma plugin, which uses the Plugin API, not the rate-limited REST API that causes the lockouts above.[4]
  • The AI generation runs inside Claude, not Figma. Figma's credits only apply to Figma's own AI features, so Flaude burns zero of them.[3]
  • The result: keep chatting and generating all day. No per-minute caps, no monthly credit meter, no multi-day cooldowns.

Sources

  1. [1] Figma Developer Docs: REST API rate limits
  2. [2] Figma Forum: Pro users report multi-day 429 lockouts
  3. [3] Figma Help Center: How AI credits work
  4. [4] Figma Developer Docs: Plugin API overview

Figma's exact limits vary by plan, seat, and file location and may change; the multi-day lockout figures come from user reports, not Figma's published spec. Check Figma's documentation for the latest numbers.

Copy a flow, then extend it

Grab a complete flow from the gallery, paste it with the plugin, then ask Claude to make it yours.

Browse flows