Figma's July 2026 release notes confirm 3D transforms for frames, vectors and text, exporting straight to CSS. Motion frames are now MCP-compatible, so coding agents get full animation context instead of a flat screenshot.
Figma's July 2026 release notes confirm 3D transforms for frames, vectors and text — rotate on the z-axis with live preview, fully editable. The result exports to CSS and connects through MCP, so the spatial design you build in Figma is what ships in code. Motion is also MCP-compatible: share an animated frame with Claude Code, Cursor or Copilot and they get full motion context, not a screenshot. Copy CSS, JSON or Motion.dev straight from Dev Mode for handoff. This isn't a gimmick — it's Figma pushing design files closer to structured, machine-readable output that agentic dev tools can actually use. If you're on Figma, it's worth 20 minutes of poking about before it's everywhere in job specs.
Coach
Open a Figma file with an animated frame, export it via Dev Mode, and see what the CSS/MCP output actually looks like — you'll want this vocabulary in interviews.
Figma's MCP catalog turns AI agents into real clients
Figma has published a live catalog of AI coding tools (Claude, Cursor, VS Code, Grok, Google Antigravity and more) that can connect to Figma via its MCP server, with several getting read-and-write access. It's the clearest sign yet that connecting an AI agent to your Figma file is becoming normal practice, not a hack.
figma.com ·
Adoption
Figma opens its canvas to AI design agents
Figma's AI agent now works natively on the canvas, generating layouts grounded in your real components and tokens rather than flat mockups. It's shipped, not speculative — but Penpot users won't get the same feature yet.
muz.li ·
Adoption
Figma's MCP Server Ships Real Team Workflows
Figma just shared four concrete internal use cases for its Dev Mode MCP server, moving it past demo territory. It's now stitching together decks, Code Connect, and Figma Make output with actual codebases.