Figma MCP write to canvas
Figma’s official MCP server can write to the canvas. Figma says that needs a Professional plan or above with edit access, and that it is free in beta and planned to become usage-based (checked November 9, 2026). FigmaMCP writes through a plugin in the desktop app instead.
Two routes to the canvas
| Figma’s write to canvas | FigmaMCP | |
|---|---|---|
| How | Figma’s MCP server | Local server and a desktop plugin |
| Plan | Professional or above, edit access | Whether your account can run a development plugin is up to Figma; not tested on every plan |
| Cost | Free in beta, planned usage-based | Free, no call quota |
| Platform | Per Figma | macOS only |
Source: Figma write to canvas. Terms may change.
How FigmaMCP writes to the canvas
FigmaMCP writes to the canvas in the Figma file you have open. Your agent, Claude Code or Codex, calls a tool on the local FigmaMCP server. The server passes the call to the FigmaMCP plugin in the Figma desktop app, and the plugin makes the change. FigmaMCP does not call Figma’s MCP server, so Figma’s write terms and limits are not part of how it works.
The write tools
FigmaMCP groups its write tools by what they change. Each name below is a real tool.
| Task | Tools |
|---|---|
| Create layers | create_frame, create_shape, create_text, create_svg |
| Arrange and change layers | node_transform, node_rename, node_group, node_clone, node_insert_child, node_delete |
| Style a layer | node_set_fill, node_set_stroke, node_set_corner_radius, node_set_effects, node_set_auto_layout |
| Edit text | text_set_content, text_set_style |
| Components | create_component, create_component_set, create_instance, instance_set_property |
| Tokens | variable_manage, style_manage, node_bind_variable, node_apply_style |
The order of a safe write
FigmaMCP makes a write in three steps. First, the agent reads. It calls page_info, then node_info, to get real IDs and names. Second, it writes. A creator such as create_frame needs a parentId and the parent’s exact name as parentNodeName. Third, it looks at the result with node_export_visual. If any step fails, the agent reads the error, fixes the input and tries again.
Rules every write follows
- One file. Writes go only to the file where the plugin is open and AI can edit this file is on. With it off, the agent can only read, and a write fails with
READ_ONLY_MODE. - Right layer, by name. To change an existing layer, the agent must pass its current name. A mismatch is refused.
- Batches first. FigmaMCP checks a whole batch before it runs, so one invalid item means no change.
- Protected layers. Locked layers, shared-library assets and the inside of component instances are not edited around.
A wrong edit that follows these rules still goes through. FigmaMCP cannot know what you meant. Review the result and use Figma version history.
Download for Mac Version 0.1.20 macOS 14+ · Intel & Apple Silicon · ~155 MB
Related: Write tools · Official MCP · Pricing
Questions
Is write to canvas free?
Does FigmaMCP use that allowance?
Which tool creates a new frame?
Why was my write refused?
Last updated: