The Figma MCP server connects Figma designs to AI agents through the Model Context Protocol, and Figma describes the flow as running in both directions. Going from design to code, an agent can generate code from selected frames and pull out variables, components and layout data, plus FigJam diagrams and Make file resources. Going from code to design, it can create and modify native Figma content directly from an MCP client, and capture live UI from a web app as design layers.
There are two ways to run it. The remote server, at https://mcp.figma.com/mcp, is the one Figma prefers: it has the broadest feature set, including writing to the canvas, and it is available on all seats and plans. The desktop server runs locally through the Figma app, is aimed at specific organizational needs, has fewer capabilities, and requires a Dev or Full seat on a paid plan. Figma lists VS Code, Cursor, Claude Code, Codex, Gemini CLI, Android Studio and Xcode among more than ten supported clients, and some support packaged workflows called skills. Code Connect keeps generated code consistent with the components your team already has.
On cost, Figma says the server is free during the beta, and that canvas-writing features will eventually be usage-based. Plan for that change rather than assuming free forever, and check the developer documentation for the current rate limits.
Verdict: the most direct way to give a coding agent your actual design system instead of a screenshot. Results depend on how tidy the Figma file is. If you are prototyping without a design file, try v0 or Lovable, and see the best MCP servers for developers for others.
Sources: Figma’s guide to the Figma MCP server, checked on September 21, 2026.
