Reading a selection's variables, layout and metadata is what most people come for, and Code Connect is what keeps the generated code on your real components rather than a lookalike. The return trip is the newer half — an agent can build frames, components and variables inside the file, which is why Figma ships skills to steer that sequence.
Figma's own server, hosted at its remote endpoint, with a desktop version for organizations that need one. It reads design context from a selection and writes native Figma content back to the canvas.
- Design context for a selection: the variables and styles it uses, layout data, and a sparse metadata view with layer ids, names, types, positions and sizes
- Code generated from a selected frame, with Code Connect mappings keeping it on your real components
- Writes to canvas — frames, components, variables and auto layout in Design files; stickies, sections, connectors and shapes in FigJam
- FigJam diagrams generated from Mermaid syntax, and FigJam boards converted to XML
- Screenshots of a selection, and downloads of up to 20 nodes as PNG, JPG, SVG or PDF plus the original uploaded source images
- Motion context — keyframe tracks, easing curves and ready-to-use CSS snippets — along with shader effects and fills
A Figma account authorized in the client. Only clients listed in Figma's MCP catalog can connect — VS Code, Cursor, Claude Code, Codex and Xcode among them. Write-to-canvas work also wants Figma's skills installed in the client, so the agent follows the right sequence when it creates or updates content.
One command — claude mcp add --transport http figma https://mcp.figma.com/mcp