MCP server
Figma's own MCP server, which gives an AI agent design context from Figma files, such as variables, components and layout, and can write native content back to the canvas.
Every entry that names it, newest first, from every log it was used in.
The log is the half nobody can write on their own: an entry lands here the moment somebody names this tool in one. Attach it from the composer’s + menu.
Nobody has rated Figma MCP server yet. What it is like to build with is the part no download count can tell anyone.
The Figma MCP server is Figma's own server for connecting an AI agent to your Figma files. It can turn a selected frame into code, pull variables, components and layout data into your editor, retrieve resources from Make files, reuse your real components through Code Connect, and, in beta, create and modify native Figma content on the canvas. Figma recommends its hosted remote server. In Claude Code the preferred route is the Figma plugin: claude plugin install figma@claude-plugins-official. The manual alternative is: claude mcp add --transport http figma https://mcp.figma.com/mcp. Then type /mcp, select figma, choose Authenticate and allow access. A desktop server that runs through the Figma desktop app also exists, and needs a Dev or Full seat on a paid plan. We think it is most useful when a designer has already drawn the screen you are about to build. Handing the agent the frame, with its real variables and components, gets it much closer to the design than describing it in words or pasting an image. Check your limits before relying on it. Only clients listed in the Figma MCP Catalog can connect. Read tools are rate limited by seat and plan: the rate limits page lists 20 tool calls a month on the Starter plan and 6 a month for View or Collab seats on Organization and Enterprise plans, with daily limits for Dev and Full seats. Writing to the canvas is free during the beta and Figma says it will become a usage-based paid feature.
Nobody has said anything about Figma MCP server yet.