Published 27 July 2026 · Source dated 1 February 2026
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.
Figma's February 2026 release notes confirm Canvas to Code — the MCP-powered link between design files and code — is now a shipped feature, not just a demo. Figma Make also gained connectors to tools like Atlassian, GitHub and Amplitude, so agents can pull real product context instead of starting from a blank prompt. The demoed workflow: sketch in FigJam, prototype in Make, align with the team, then build with Figma MCP and a coding agent — all without leaving Figma's ecosystem. For juniors on Figma, this means dev handoff conversations are shifting from 'here's the spec' to 'here's the context the AI already has.' Worth understanding even if your team isn't using agents yet, because clients and senior devs increasingly will.
Coach
Watch the Figma release notes video and note one workflow (FigJam → Make → MCP) you could try on a small personal project this week.
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 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.