FigmaMCP

Figma MCP use cases

This is the FigmaMCP use-cases hub. FigmaMCP connects Claude Code or Codex to the Figma file you have open on your Mac. Each page below covers one job: bulk edits, a read-only audit, building a design from code, or reading a design to write code. The table shows which page and which tools fit your task.

Pick a page by task

FigmaMCP use-case pages
Your taskPageMain tools
Rename, restyle or replace text across many layersBulk edit Figma layersnode_rename, text_set_content, node_apply_style, node_delete
Change a live file from Claude Code or Codex in generalEdit Figma with AInode_rename, text_set_content, create_frame, node_bind_variable, annotation_set
Build frames, text and shapes from codeCode to canvascreate_frame, create_text, create_svg, node_set_auto_layout
Read a design and write the code yourselfDesign to codepage_info, node_info, variable_list, node_export_visual
List unstyled layers, unnamed frames and missing bindingsAudit a Figma filepage_info, node_info, style_list, variable_list, component_list

Reading is safer than writing

FigmaMCP splits its tools into reads and writes. The read tools never change the file. They are page_info, node_info, style_list, variable_list, component_list, annotation_list, reaction_list and instance_get_overrides. The audit and design-to-code pages use mostly these. If you are new to the tool, start with one of them.

What every write has in common

FigmaMCP checks each write before it runs. The edit goes only to the open file where the plugin’s AI can edit this file switch is on. Each edit names its target layer, and the name must match the layer’s real name. Batch tools check every item first, so one invalid item stops the call with no change. A refused call returns a structured error, such as NAME_MISMATCH or READ_ONLY_MODE, and the agent can correct the request. A wrong edit that follows the rules still goes through, so keep Figma version history on.

Which job to start with

Starting points
If you wantStart withWhy
To see what the agent finds, with no riskAudit a Figma fileIt only reads.
To save time on repeated editsBulk edit Figma layersCheck one result by eye, then run the rest.
To move a screen from code into FigmaCode to canvasBuild one frame first, then check the picture.
To turn a design into codeDesign to codeThe agent reads layers, tokens and a picture. FigmaMCP does not write the code.

Limits that apply to every page

Each page lists its own tools, steps and errors. For the full tool list, see all tools.

Download for Mac Version 0.1.20 macOS 14+ · Intel & Apple Silicon · ~155 MB

Questions

Which use case should I try first?
Try the audit. It only reads, so it cannot change your file. Then try a small bulk edit on a duplicate page.
Do these pages need different setup?
No. Setup is the same for every job: install the Mac app, open your file in the Figma desktop app and ask your agent.
Can FigmaMCP turn a design into code by itself?
No. FigmaMCP lets your agent read the design. The agent writes the code in your project with its own file tools.
Can it import an HTML file into Figma?
No. There is no HTML importer. The agent reads your code and builds frames, text and shapes with the create tools.

Last updated: