Figma's MCP Server Now Hands Agents Real Code

Figma's Model Context Protocol server now lets AI agents read the actual underlying code of Figma Make apps, not just infer from screenshots. It's an expansion of the Dev Mode MCP server Figma has run since 2025.

Figma's Model Context Protocol server now lets AI agents read the actual underlying code of apps built in Figma Make — not just infer from screenshots. First launched as the Dev Mode MCP server in 2025, it's been expanded through 2026 to expose more structured context (variables, component maps, Code Connect mappings) directly to agentic IDEs like Claude Code and Cursor. Practically: an agent can pull real component structure instead of guessing from pixels, cutting the 'that's not quite right' rebuild loop. It's a real, shipped capability rather than a roadmap promise — but it's new enough that most teams haven't built workflows around it yet, so getting hands-on now is a genuine edge, not just resume-padding.

Related in AI workflows

Adoption

MCP is quietly becoming the default for AI dev tools

Cursor's Model Context Protocol integrations have passed ten essential connectors linking AI assistants to databases, APIs and design tools, with more expected across the product lifecycle. It's less flashy than agent demos, but it's the plumbing that makes those demos actually work.

zoer.ai1 Jan

Adoption

MCP servers are now table stakes for AI agents

MCP (Model Context Protocol) has become the standard bridge letting AI agents like Cursor, Claude Code and Figma's own agent pull in real project context. It's no longer a niche integration — it's expected infrastructure across tools.

nxcode.io1 Jul

Hype

Figma Ships a Canvas-Native AI Design Agent

Figma's new agent works directly on the canvas via the MCP server's use_figma tool, not just in a chat window. It can remix styles, generate screens, and make bulk edits using your actual design system.

figma.com26 Mar