Figma MCP components
FigmaMCP lets Claude Code or Codex turn frames into components, combine them into variant sets, add component properties, place instances and copy overrides between instances in the Figma file you have open. You describe the component. The agent picks the tools and passes each layer name back exactly.
Component tools
| Task | Tools |
|---|---|
| List components | component_list |
| Create a component or a set of variants | create_component, create_component_set |
| Add or change a property | component_manage_property, component_delete_property |
| Place an instance | create_instance |
| Change an instance | instance_set_property, instance_set_overrides, instance_get_overrides |
Build a button with variants
FigmaMCP builds a variant set in two stages. First create_component converts an existing frame into a main component. It takes the frame’s ID and exact name. Then create_component_set combines components into one set.
- Read each frame with
node_info. Each one must be unlocked and not inside an instance. - Convert each frame with
create_component. - Choose property names, for example
Size. Give every component one value per property, such asSmall. - Read the parent that will hold the set, then call
create_component_setwithparentIdandparentNodeName.
Every combination of values must be unique. A value cannot be empty, and it cannot contain = or ,. The parent cannot be one of the components you combine. A component that already sits in another set cannot be combined. If the combine fails halfway, the error can carry details.partialMutation: true. Read that evidence before you retry.
Properties and instances
FigmaMCP’s component_manage_property adds or edits a property on a main component or a set. The property type is BOOLEAN, TEXT or INSTANCE_SWAP. ADD needs a type and a default value. EDIT can rename the property or change its default. component_delete_property removes a property, and that change reaches every instance.
create_instance places an instance from a componentId, or from a componentKey for a library component. It needs x, y and a named parent. Pass a variant, not a component set. instance_set_property sets one property on one instance. instance_get_overrides reads the overrides of a source instance. instance_set_overrides applies them to several target instances. It swaps each target to the source component first.
Limits and errors
| Error or message | Meaning | What to do |
|---|---|---|
NAME_MISMATCH | The name you sent is not the layer’s current name. | Read the layer again with node_info and retry. |
READ_ONLY_MODE | The AI can edit this file switch is off. | Turn it on in the plugin. |
Operation Denied: inside a component instance | Structural edits such as delete or group are blocked inside an instance. | Edit the main component, or use instance_set_property and overrides. |
Operation Denied: remote library asset | Main components from a shared library are read-only in this file. | Edit them in the source library. Instances of them can still take overrides. |
Operation Denied: duplicate variant combination | Two components in a set have the same values. | Give each component a unique combination. |
FigmaMCP can place an instance of a library component with componentKey. Read the key from an existing instance’s main component, and make sure the library is enabled for the file. Locked layers are not edited. See Figma MCP design system for styles and variables.
Download for Mac Version 0.1.20 macOS 14+ · Intel & Apple Silicon · ~155 MB
Related: All tools · Design system · Variables
Questions
Can it build a button with variants?
Can it edit a library component?
How do I copy text and property changes from one instance to others?
Can it change a layer inside an instance?
Last updated: