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.

Figma's Dev Mode MCP server is out of the 'just a beta' phase — the team shared four real internal use cases: updating decks from code, syncing Code Connect so components track your codebase, and bridging Figma Make output straight into a repo. For anyone on Figma + Penpot, this is the clearest evidence yet that MCP is becoming the standard bridge between design files and AI coding agents, not a novelty demo. If you haven't touched Dev Mode or Code Connect, give it 20 minutes this week — even just reading how a design-systems team wired it up shows you where 'AI-fluent designer' skills are heading.

Related in Design tools

Adoption

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.com15 Jan

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.li24 Mar

Adoption

Figma Adds 3D Transforms & MCP-Ready Motion

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.

releasebot.io1 Jul