Connect Claude to Figma

Four steps, about a minute. It runs over a live WebSocket on your own Claude subscription, so there’s no API key, no Figma API limits and no AI credits burned.

Claude, Flaude Pro and Figma connected

What the MCP does

Copy a whole flow, not a screenshot

Paste any flow into Figma and every screen arrives as real, named, editable layers — the layer tree included.

An ElevenLabs sign-up flow pasted into Figma with its full layer tree intact

Ask Flaude to make it yours

Claude reads those layers, then recolors, rewrites and rebrands the whole flow — same structure, your product.

The same flow restyled end to end into Flaude branding

Never hits a Figma API limit

It works through the Figma plugin, not the REST API, so there is no per-minute cap to trip and no 429 lockout to wait out.

Claude connected to Figma through the Flaude plugin

It works in your own file

Claude edits the file you already have open. Nothing to export, nothing to import, no copy of your work sent anywhere.

Flaude connected live to a Figma file, reading its brand styles and tokens

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.

Request limits

Figma's own API

~10–50 calls a minute. Figma's REST API is rate-limited by plan and seat — roughly 10/min on free Starter, 50/min on Pro.[1]

Through Flaude

No REST limit at all. Flaude talks through the Figma plugin, which uses the Plugin API — not the rate-limited REST API.[4]

What happens if you go over

Figma's own API

Lockouts lasting days. Go over and you get 429s. Designers report a handful of calls triggering multi-day cooldowns.[2]

Through Flaude

Nothing to go over. No per-minute cap means no 429s and no cooldown to wait out.

AI cost

Figma's own API

3,000 credits a month. Figma's own AI runs on monthly credits — 3,000 on a Professional Full seat, 500 on others, and they don't roll over.[3]

Through Flaude

Zero Figma credits. Generation runs inside Claude, on the subscription you already pay for. Figma's credits only apply to Figma's own AI.[3]

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.

01

Download the plugin

Grab flaude-plugin.zip and unzip it anywhere on your machine.

PluginsDevelopmentImport from manifest
02

Import it into Figma

In Figma: Plugins › Development › Import plugin from manifest → pick manifest.json from the unzipped folder.

https://flaude.app/mcp/…
03

Paste your URL into Claude

Open Flaude in Figma → Settings → copy your MCP URL, then add it in Claude under Settings › Connectors.

Claude designing inside a Figma file
04

Design with Claude

Ask Claude to build or restyle a screen. It appears on your canvas as real, editable layers.

Flaude installs from a manifest rather than the Figma Community, which is why step 2 exists. Figma keeps imported plugins in Plugins › Development, so it stays one click away in every file after the first import.