How to Connect the Figma MCP Server to Claude Code (2026)
The short answer
Install Figma’s Claude Code plugin (claude plugin install figma@claude-plugins-official), sign in once, then paste a “Copy link to selection” URL from Figma into Claude Code and ask it to build that frame. The whole setup takes about five minutes. Commands and limits below are from Figma’s help center, read on November 21, 2026.
What you need
- Claude Code installed and signed in.
- A Figma account. Any plan connects, but a Dev or Full seat on a paid plan is what makes it usable day to day (up to 200 read calls a day instead of about 20 a month).
- Optional: Code Connect set up for your component library.
Step 1: Install the remote server with the plugin (recommended)
- In your terminal, run
claude plugin install figma@claude-plugins-official. - Restart Claude Code if it was running.
- Type
/plugin, press the right arrow to the Installed tab, select figma and press Enter twice. - In the browser page that opens, click Allow access.
- Back in Claude Code,
/pluginshould show figma as connected.
The plugin bundles the MCP server settings and Figma’s skills — Markdown instructions that help the agent use Figma’s tools in the right order.
Done when: /plugin lists figma as connected.
Step 1 (alternative): Add the server manually
If your organization blocks plugins:
- Run
claude mcp add --transport http figma https://mcp.figma.com/mcp(add--scope userto make it available in every project). - Start a new Claude Code session, type
/mcp, select figma, choose Authenticate and click Allow access. - Install Figma’s skills separately if you want them.
Done when: Claude Code prints “Authentication successful. Connected to figma.”
Step 1 (enterprise): The desktop server
Open the Figma desktop app, open a design file, switch to Dev Mode (Shift+D), and in the MCP server section click Enable desktop MCP server. Then run claude mcp add --transport http figma-desktop http://127.0.0.1:3845/mcp and restart Claude Code. Use this only if your organization requires local connections; it needs a Dev or Full seat on a paid plan and lacks some remote features.
Step 2: Give Claude Code a design
- In Figma, right-click the frame or layer and choose Copy link to selection.
- In Claude Code, paste the link with an instruction, for example: “Implement this screen in our Next.js app. Use components from src/components/ui and colours from our Tailwind theme. Do not create new button or input components.”
- Review the diff and run the app.
The server returns design context that looks like React and Tailwind regardless of your stack, so always name the target framework (“in SwiftUI”, “as a Vue SFC”).
Step 3: Make it reuse your components
- Code Connect maps Figma components to files in your repo, so the agent imports your
<Card>instead of writing a new one. On Professional plans only one framework can be active at a time. - Variables carry design tokens; ask the agent to use the variable names.
- Rules: put conventions in your project’s
CLAUDE.mdso every session follows them.
Rate limits and costs
| Seat / plan | Read tool calls |
|---|---|
| Starter plan, View or Collab seat | ~20 per month |
| Full or Dev seat — Professional, Education, Organization | Up to 200 per day (10–15 per minute) |
| Full or Dev seat — Enterprise | Up to 600 per day (20 per minute) |
Writing to the canvas (creating frames and components from Claude Code) needs the remote server and a Full seat outside your drafts; it is free in beta and will become usage-based. Write tools and Figma AI credit actions are exempt from the read limits.
Troubleshooting
- No figma tools: confirm with
/mcp; only clients in Figma’s MCP catalog can connect. - Rate limited: select one larger frame instead of many small ones, or upgrade the seat.
- Admin blocked it: since November 17, 2026, Organization and Enterprise admins can allowlist approved MCP clients; request access from the prompt.
Choosing between this and other design-to-code tools? See Figma MCP vs Builder.io vs Anima. More on MCP in agents: how to use MCP servers with coding agents.
Last verified: November 21, 2026.