Figma Just Let AI Agents Write to Your Canvas — What the use_figma MCP Beta Actually Does

For years, AI could tell you how to design something. Now it can actually do it — directly in Figma. On March 24, 2026, Figma launched the use_figma MCP (Model Context Protocol) tool in open beta, giving AI agents write access to the design canvas for the first time.

The announcement went viral in the developer and design community within hours. Figma's tweet — "Now you can use AI agents to design directly on the Figma canvas" — was one of the most shared AI posts of the week. The r/ClaudeCode subreddit lit up with early tests.

Here is what it actually does, what it cannot do yet, and what it means for your workflow.

What use_figma Actually Does

The use_figma tool is part of Figma's remote MCP server. Once enabled, it gives any connected AI agent read and write access to your Figma files — not just reading designs, but creating and modifying native Figma content:

• Frames and layers: Create, move, resize, and nest frames using your design system's token values
• Components: Instantiate existing components from your library, with correct props and variants
• Variables and tokens: Apply color, spacing, and typography tokens — not hardcoded values
• Auto-layout: Set up responsive auto-layout constraints the same way a designer would
• Self-healing loop: Agents screenshot their own output, compare against the intended design, and iterate on mismatches — operating on Figma's native node structure, not just pixels

The key differentiator is design-system awareness. Previous AI design tools generated generic outputs. use_figma works within your actual component library, respecting your team's naming conventions and token structure. If your button component is called Button/Primary/Large, the agent uses that exact component — not a lookalike rectangle.

Figma Skills: Teaching Agents Your Workflow

Alongside use_figma, Figma introduced a Skills framework — markdown files that teach agents how to operate within a specific team's design workflow. Nine community-built skills launched on day one:

Teams can also write custom skills for their own workflows — anything from "always use our brand grid system" to "generate a 3-state button variant for every new component."

Which AI Agents Are Supported

The Figma MCP server works with any MCP-compatible client. Supported at launch:

• Augment
• Claude Code (Anthropic)
• Codex (OpenAI)
• Copilot CLI and Copilot in VS Code (Microsoft)
• Cursor
• Factory
• Firebender
• Warp

Claude Code is on the list — which means Happycapy users with Claude Code skills installed can connect to Figma's remote MCP server and use use_figma directly from the Happycapy agent environment.

Limitations to Know Before You Dive In

The beta is promising — but it is still a beta. Current limitations:

Figma MCP vs. Full AI Design Workflow

use_figma solves a specific part of the design workflow: getting AI to produce canvas-native outputs within your design system, not generic mockups. That is genuinely valuable for teams who spend hours cleaning up AI-generated designs.

But design is one step in a larger workflow. After a design is done, someone needs to write the product brief, communicate it to stakeholders, hand off specs to developers, track feedback, and coordinate the launch. None of that happens in Figma.

Happycapy handles the workflow that surrounds design: researching brief requirements, drafting copy for components, communicating with clients via Capymail, managing tasks via Mac Bridge, and remembering every project detail across sessions — so your AI agent is not starting from scratch every time you open a new conversation.

How to Connect Claude Code to Figma MCP

Generate your token in Figma: Settings → Security → Personal access tokens. The remote MCP server is free during the beta. Full seats get unlimited write access; Starter seats get 6 tool calls per month.

Frequently Asked Questions

Sources: Figma Blog "Agents, Meet the Figma Canvas" (figma.com, March 24, 2026), Figma Help Center MCP Guide, GitHub figma/mcp-server-guide, Figma on X (@figma, March 24, 2026).