Figma's MCP server now speaks to Claude Code

Figma's MCP server now plugs straight into Claude Code, turning your Figma files into a live source an AI coding agent can read, edit and sync with production code. It's a real step in closing the design-to-code gap without leaving your existing tool stack.

Builder.io's walkthrough shows Claude Code pulling live Figma files via the MCP server, translating frames into working components, then pushing changes back — no manual redlining required. For junior designers flipping between Figma and Penpot, this matters: MCP is becoming the connective tissue between design tools and AI coding agents, not a Figma-only trick. Other MCP servers exist for different tools too, so expect this pattern to spread across your stack. This is adoption, not hype — real teams are using it in production handoff right now. Worth understanding even if you never touch code: interviewers are starting to ask how your files feed into AI tooling downstream.

Related in Design tools

Adoption

Agent platforms are quietly joining your toolkit

A wave of AI agent platforms (Sana, Lindy and others) are moving from HR and finance into everyday work tools, not just design apps. Worth knowing the landscape even if you're Figma/Penpot-first.

sanalabs.com1 Jun

Adoption

Figma's Feb 2026 release: Canvas to Code ships

Figma's February 2026 release notes confirm the MCP-powered Canvas to Code link between design and code is now a shipped feature. Figma Make also gained connectors to Atlassian, GitHub and Amplitude so agents get real product context instead of a blank prompt.

youtube.com1 Feb

Adoption

Figma's MCP server now bridges IDE and canvas

Figma's MCP Server update connects your IDE, AI agents, and Figma Make straight to your design files, with Code Connect feeding real component code into the loop. It's dev-facing first, but it changes what 'good file hygiene' means for designers too.

figma.com10 Jun