Published 23 July 2026 · Source dated 26 March 2026
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's new canvas-native agent (built on the MCP server's use_figma tool) can generate screens, remix your existing styles, and make bulk edits directly on the canvas — not just spit out code in a sidebar. It reads your file's real structure, components, and 'skills' (context you give it about team decisions), so output is meant to match your design system rather than generic AI output.
It's brand new, so treat early results with a critical eye — check spacing, token usage, and accessibility by hand before shipping anything it produces.
Coach
Try the Figma agent on a throwaway file — ask it to remix one screen using your styles, then manually check spacing and contrast before trusting the output.
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.ai ·
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.io ·
Adoption
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.