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
| Your task | Page | Main tools |
|---|---|---|
| Rename, restyle or replace text across many layers | Bulk edit Figma layers | node_rename, text_set_content, node_apply_style, node_delete |
| Change a live file from Claude Code or Codex in general | Edit Figma with AI | node_rename, text_set_content, create_frame, node_bind_variable, annotation_set |
| Build frames, text and shapes from code | Code to canvas | create_frame, create_text, create_svg, node_set_auto_layout |
| Read a design and write the code yourself | Design to code | page_info, node_info, variable_list, node_export_visual |
| List unstyled layers, unnamed frames and missing bindings | Audit a Figma file | page_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
| If you want | Start with | Why |
|---|---|---|
| To see what the agent finds, with no risk | Audit a Figma file | It only reads. |
| To save time on repeated edits | Bulk edit Figma layers | Check one result by eye, then run the rest. |
| To move a screen from code into Figma | Code to canvas | Build one frame first, then check the picture. |
| To turn a design into code | Design to code | The agent reads layers, tokens and a picture. FigmaMCP does not write the code. |
Limits that apply to every page
- macOS only for now, and the Figma desktop app is required. It does not run in the browser.
- FigmaMCP is not on Figma Community. The Mac app installs the plugin for you.
- Features that belong to Figma itself, such as Dev Mode, are not included.
- FigmaMCP is independent. It is not affiliated with Figma, Inc.
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?
Do these pages need different setup?
Can FigmaMCP turn a design into code by itself?
Can it import an HTML file into Figma?
Last updated: