Skip to main content
  • Pricing
Tutorials

Claude Code and Figma in both directions: set up the Figma MCP server and know its limits

By Oakgen TeamPublished 3 min read

Share
Claude Code and Figma in both directions: set up the Figma MCP server and know its limits

Claude Code can work with Figma in both directions through Figma's MCP server. It can read your design files and turn selected frames into code, and with the remote server it can push a live web page back into Figma as editable layers. This guide covers which server to pick, the exact setup commands, and the limits Figma documents as of 2026-11-19.

What "two-way" means in practice

According to Figma's help center, the Figma MCP server gives Claude Code structured access to your Figma files. Going from design to code, Claude Code can read design context (components, variables, layout data, FigJam content and Make resources), generate code from selected frames, and use Code Connect to line the output up with your real components.

Going from code to design, Figma says Claude Code can write to the canvas, creating or updating Figma content. Figma's developer docs describe the code-to-canvas feature as turning live UI from your browser (production, staging or localhost) into editable design layers. That feature needs the remote server and is limited to select clients.

Choose the remote or the desktop server

Figma offers two server types. The comparison below uses only what Figma's pages state.

Remote serverDesktop server
Endpointhttps://mcp.figma.com/mcphttp://127.0.0.1:3845/mcp
Needs the Figma desktop appNoYes
Seat requirementListed under all plans, requires Claude CodeDev or Full seat on a qualifying paid plan
Canvas writes and code to canvasSupportedNot supported, they require the remote server
Figma's guidanceBroadest feature set, best for most usersFor specific organization and enterprise needs

For most people the remote server is the right choice.

Set it up in Claude Code

Option 1, the plugin (recommended by Figma).

  1. In a terminal, run claude plugin install figma@claude-plugins-official.
  2. Restart Claude Code if it was running.
  3. Type /plugin, open the Installed tab, select figma and press Enter to sign in.
  4. Click Allow access in the browser, return to Claude Code and run /plugin again to confirm figma shows as connected.

Option 2, add the server by hand (no Figma skills).

  1. Run claude mcp add --transport http figma https://mcp.figma.com/mcp. Add --scope user to make it available in every project.
  2. Start a new session, type /mcp, select figma and choose Authenticate.
  3. Click Allow access in the browser and check /mcp again.

Figma notes that clients do not open Figma links by themselves. You copy the link to a selection in Figma, paste it into your prompt, and the client extracts the node ID from it.

Where the configuration lives

Claude Code's documentation defines three scopes. Local is the default: it loads only in the current project, is not shared and is stored in ~/.claude.json. Project scope writes a .mcp.json in the project root so the team shares it through version control. User scope loads in all your projects and is not shared. When the same server name exists in several scopes, the order of precedence is local, then project, then user. Figma signs in through the browser, so there is no token to paste into a shared file.

Check these limits before you rely on it

  • Client catalog. Figma says only clients listed in its MCP catalog can connect to the remote server. Claude Code is named among the supported clients.
  • Seats and cost. Writing outside drafts requires a Full seat. Figma's developer docs say write to canvas is free during beta and will eventually become usage-based.
  • Government accounts. The help center says Code to Canvas, Code Connect UI and Figma Motion tools are unavailable on the Government plan and gives a separate endpoint, https://mcp.figma-gov.com/mcp. The developer docs say Figma for Government supports only the desktop server for now. The two pages differ, so confirm with Figma if you are on that plan.
  • Rate limits. Figma documents them on a separate page. Read it before wiring the server into automation.

A loop worth trying

This is a suggested workflow built from the documented capabilities, not an official Figma procedure.

  1. In Figma, copy the link to a frame and ask Claude Code to build it as a component, reusing the components you already have through Code Connect.
  2. Run the result on localhost and review it in the browser.
  3. Use code to canvas to send the running page into Figma, so a designer can adjust spacing or colour on real layers.
  4. Copy the link to the revised frame and ask Claude Code to reconcile the code with the new design.

Keep the connection safe

Claude Code's docs tell you to verify that you trust each MCP server before connecting it, and warn that servers which fetch external content can expose you to prompt injection. Removing a remote server deletes the stored OAuth tokens locally but does not revoke them at the authorization server. To revoke access, run claude mcp logout figma before claude mcp remove figma.

Take this further with Oakgen Agent

Agent can research Figma's current MCP documentation with web search, write the checklist and handoff template, and save them as a downloadable markdown or docx file.

Looking for a recap of one specific YouTube video? The YouTube Summarizer does that today.

Open this task in Oakgen Agent

The prompt is filled in for you. Nothing is sent until you press send.

Open in Oakgen Agent

Frequently asked questions

Do I need the Figma desktop app to use Claude Code with Figma?

Not for the remote server. Figma's developer documentation says the remote server is hosted at https://mcp.figma.com/mcp and does not require the Figma desktop app. The desktop server is the one that runs locally through the desktop app, and Figma describes it as intended for specific organization and enterprise needs. Figma recommends the remote server for most users because it has the broadest set of features. Information as of 2026-11-19.

Should I install the Figma plugin or add the server manually?

Figma lists the plugin as the recommended route for Claude Code: run claude plugin install figma@claude-plugins-official. The plugin bundles the server settings and Figma's skills. Adding the server manually with claude mcp add --transport http figma https://mcp.figma.com/mcp works, but Figma says the manual method does not install its skills, which its docs say improve reliability. If plugin installation is blocked by your organization, the manual route is the fallback.

Can Claude Code write back to Figma?

Yes, with limits. Figma's help center says Claude Code can write to the canvas and can send live web interfaces to Figma as editable layers. Figma's developer docs add that writing requires the remote server, that writing outside drafts needs a Full seat, and that write to canvas is free during beta and will eventually become usage-based. Figma also says write to canvas and code to canvas are still being improved.

How do I check that the connection works?

Start a new Claude Code session, type /mcp, select figma, choose Authenticate and click Allow access in the browser. Figma's docs say you should then see the message that authentication succeeded and that Claude Code is connected to figma. If you used the plugin, type /plugin and confirm figma shows as connected.

Sources

  1. Figma Developer Docs, Remote server installation, Claude Code section (read 2026-11-19)
  2. Figma Help Center, Figma MCP server for Claude Code (read 2026-11-19)
  3. Figma Developer Docs, Figma MCP server introduction (read 2026-11-19)
  4. Claude Code documentation, Connect Claude Code to tools via MCP (read 2026-11-19)
Share