Fetching from the wire…
Top 5 · 2026-03-25 · source-backed
Figma released its MCP server in open beta, and this one matters more than most MCP launches. AI agents can now read, create, and edit components directly on the Figma canvas using your design system variables. The use_figma tool works with Claude Code, Cursor, Codex, Copilot CLI, and any MCP-compatible client.
I've been waiting for this. My design background is the reason I can ship products that don't look like developer projects, but the gap between design intent and code output has always been a manual bridge. Figma's MCP server is the first real attempt to let agents cross that gap natively.
The skills system is what makes it actually useful. Figma published figma-use, a markdown-based skill file that teaches agents how to behave on the canvas. If you've written a CLAUDE.md file, you already understand the pattern. Install it, and the agent knows how to create frames, apply auto layout, reference design system tokens, and build components that respect your constraints. Without the skill, agents produce garbage on the canvas. With it, they produce usable designs.
Setup is simple: claude mcp add --transport http figma https://mcp.figma.com/mcp. Or claude plugin install figma@claude-plugins-official. The API will eventually be paid, but it's free during beta while Figma works out agentic seat pricing.
For builders who've been running design-to-code workflows manually, this changes the loop. You can now describe a component in natural language, have Claude Code create it in Figma, review it visually, then generate the React/CSS from the actual design. The design file becomes the source of truth instead of a reference screenshot. Combined with Google Stitch's DESIGN.md export that gives coding agents design system awareness, we're getting close to a real design-to-code pipeline that doesn't require a human copying hex values.
Each link below shares sources, entities, or timing with this story.
Figma supports Cursor / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Figma supports Cursor); both cover Canvas, Claude Code, CSS, Cursor; cite the same source (Google Stitch's DESIGN.md export).
Notion uses Cursor / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Notion uses Cursor); both cover Claude, Claude Code, Codex, Cursor; overlapping topics (agent, claude, code, component, design).
Cursor uses MCP / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor uses MCP); both cover Claude Code, Cursor, DESIGN, Google Stitch; cite the same source (Google Stitch's DESIGN.md export).
Cursor uses MCP / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor uses MCP); both cover Claude Code, CSS, Cursor, Figma; overlapping topics (agent, canva, claude, code, cursor).
Cursor partners with Stripe / Shared entities / Shared topic
Linked by a graph relationship (Cursor partners with Stripe); both cover CLAUDE, Claude Code, DESIGN, Google Stitch; overlapping topics (agent, claude, code, design, file).
Cursor uses MCP / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Cursor uses MCP); both cover Claude Code, Combined, CSS, Cursor; overlapping topics (agent, been, code).
chrome-devtools-mcp supports Cursor / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (chrome-devtools-mcp supports Cursor); both cover Claude Code, CSS, Cursor, MCP; overlapping topics (agent, been, code, component).
Cursor uses MCP / Shared entities / Same source / Shared topic / What happened next
Linked by a graph relationship (Cursor uses MCP); both cover Claude Code, Cursor, Figma, MCP; cite the same source (Figma released its MCP server in open beta).