Can AI agents automate Figma?

Figma Design is automatable today through a vendor-hosted MCP server and a public REST API. The remote MCP endpoint at mcp.figma.com supplies design context, screenshots, variables, Code Connect maps, and, during a beta that Figma says will become usage-based, write-to-canvas tools that create and update frames, components, variables, and auto layout. A desktop MCP server also exists. Only clients in Figma's MCP catalog may connect. Write tools need a Full seat and file edit permission; Starter and View or Collab seats are limited to six MCP tool calls per month. The REST API at api.figma.com is OpenAPI-described and authenticates with OAuth 2.0, personal access tokens, or Organization and Enterprise plan access tokens. It can read files, nodes, images, comments, versions, components, and variables, and it can write comments, variables, and dev resources. File GET requests are limited to six per month on Starter and to 10–20 per minute for Dev or Full seats on paid plans. Plugins and widgets read and write the open editor file. The official CLI is Code Connect, which maps design components to code rather than operating files. Zapier and Make have Figma connectors with plan and seat gates; n8n ships a beta webhook trigger that requires a Professional plan; Microsoft's connector catalog had no Figma Power Automate connector on 2026-08-21. Computer-use viability is unassessed. FigJam, Slides, and Sites share some MCP and Plugin surfaces but are not scored as separate products here.

Best path today: mcp · Overall automatability: 7/10