Figma announced an expansion of its MCP (Model Context Protocol) Server, enabling AI agents and developers to access design context in the browser and local IDE, beyond the desktop. This update emphasizes remote access and integrates with Figma Make: AI agents can directly access prototype code and design data generated by Make, enabling more accurate app generation or modification. The official also showcased a "Design Snapshot to Editable Layer" workflow, making it easier to pull components, variables, and layout information from within a conversation and generate code based on it.
Figma also released the all-new Code Connect UI (Beta) , which allows one-click mapping of code repositories to Figma components within organizations and enterprises, narrowing the gap between design and implementation. MCP Server's Guides and Dev Mode integration is now live, allowing MCP clients like VS Code, Cursor, and Windsurf to directly access the tool, remotely extract file structure and style variables, and execute build tasks.
Frequently Asked Questions
Q: What are the key enhancements to MCP Server?
A: New remote access scenarios, connection with Figma Make's code/design context, and support for calling design data directly in the IDE.
Q: What is the purpose of the Code Connect UI?
A: In the Org/Enterprise seat, map the GitHub code to the Figma components, so that the generator can produce code based on the real component constraints.
Q: Which tools/editors are supported?
A: Official examples and reports mention MCP-compatible clients such as VS Code, Cursor, and Windsurf.
Q: Who is MCP Server suitable for?
A: Teams that need AI agents to "understand the design and generate code according to the component system", especially in the scenario of making prototypes to code landing.
Q: Is there any official documentation?
A: Figma provides a Dev Mode MCP Server guide and resource library entry, including access steps and permission instructions.
