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's MCP Catalog lists which AI tools can talk to your Figma files, and how much they're allowed to do. Some, like Claude and Kiro, now have both read and write access to Design and FigJam files, not just read-only exports. This matters because it's Figma officially endorsing agent-to-canvas workflows, not just third-party hacks. For a junior on Figma + Penpot, the practical bit: if you're pairing with an AI coding tool, check whether it's already on this list before wiring up a custom integration — someone's probably built and tested it. This is adoption, not hype: it's Figma's own product documentation, describing tools already in production use, not a demo.

Related in Design tools

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'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.com25 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