Published 26 July 2026 · Source dated 10 June 2026
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's latest MCP Server update — covered on Figma's blog — connects your IDE, AI agents, and Figma Make directly to your design files. Code Connect now feeds Figma's MCP server so tools like Cursor or Claude Code can pull real component code, not just guess from screenshots. It's aimed at devs first, but as a junior using Figma + Penpot, it's worth knowing how your files get consumed downstream — sloppy naming and unstructured layers now break AI pipelines too, not just handoff docs. This is adoption, not hype: Figma's shipping it as a beta-to-GA product feature, not a demo.
Coach
open one Figma file you'd hand off to a dev, rename any vague layers ('Frame 27', 'Rectangle 12') to real component names — that's exactly what MCP tools now read.
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.com ·
Adoption
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 ·
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.