Setting up the Figma MCP Server

The Figma MCP server brings design context from Figma files into AI coding workflows. Setup uses OAuth, but the practical benefit depends heavily on your own Figma plan.

First: check your Figma plan

The server itself has no extra fee, but without a paid Figma plan with a Dev or Full seat, only a handful of calls per month are possible (Starter plan: up to 20/month, View/Collab seat on a paid plan: up to 6/month). For regular use, at least a Dev or Full seat on a Professional, Organization, or Enterprise plan is needed.

Setting up in Claude Code

The recommended way is the official Figma plugin, which includes MCP settings and matching agent skills:

claude plugin install figma@claude-plugins-official

Alternatively, set it up manually:

claude mcp add --transport http figma https://mcp.figma.com/mcp

Adding --scope user makes the server available in all projects instead of only the current one. Then run /mcp in Claude Code, select "figma", choose "Authenticate", and confirm access in the browser window that opens.

Setting up in other clients

Figma also documents setup for Codex, Cursor, VS Code, and Xcode; the details differ by client, but the underlying mechanism (remote server over HTTP, OAuth sign-in) stays the same.

Using write access deliberately

With the right skills, the agent can not only read but also directly create or modify frames, components, and variables in Figma Design files, and edit FigJam boards. Since the server operates with the signed-in account's permissions, it's advisable to try new write workflows on a test file first before running them against production design systems.

Verifying the setup

After signing in, run the whoami tool (or ask the agent to) to confirm the email address used and the associated Figma plans and seat types. Then test with a harmless, read-only task, such as "Describe the components in this Figma frame."

Common connection issues

If sign-in hangs in the browser window after confirming, a client restart and another attempt via /mcp usually resolves it. If whoami shows the wrong or unexpected Figma plan, it may be because multiple Figma accounts are signed in in the browser — make sure the correct account is active before signing in.

Keeping usage limits in view

Since usage limits vary significantly by Figma plan and seat type, it's worth checking the current limits in the Figma account before heavier use. If the monthly or daily quota is reached, the server reports this via an error that can only be resolved by waiting for the next window or upgrading the plan.

Source: developers.figma.com/docs/figma-mcp-server/ (Introduction, Remote server installation, Rate limits & access), checked on 2026-09-06.