Figma MCP Server

Official Figma MCP server that lets AI agents read design context from Figma files and generate code from frames.

Description

The Figma MCP server brings Figma design context directly into AI coding workflows: read variables, components, and layout data from Figma files, turn selected frames into code, keep generated code aligned with your own codebase via Code Connect, and retrieve resources from Figma Make files. With the right skills, the agent can also write directly to the canvas — creating or updating frames, components, variables, and auto layout in Figma Design files, editing FigJam boards with stickies, sections, connectors, and shapes, and generating architecture or ER diagrams in FigJam from prompts, code, or structured input. On supported clients, it can additionally capture a web app's live rendered UI into a new Figma file.

Access depends on your Figma plan

Figma runs the server exclusively as a hosted service at https://mcp.figma.com/mcp. Access and usage limits depend on your Figma plan and seat type: on the Starter plan it's up to 20 calls per month, and with a View or Collab seat on a paid plan only up to 6 per month. Only a Dev or Full seat on a paid plan (Professional, Organization, or Enterprise) unlocks a practical quota — up to 200 calls per day on Professional, up to 600 per day on Enterprise, each with an additional per-minute cap. A desktop variant of the server is available for organizations with special requirements, but Figma recommends the remote option for most users. Only MCP clients listed in the Figma MCP Catalog can connect, including Claude Code, Cursor, VS Code, and Xcode.

Why a dedicated MCP server instead of generic screenshot analysis

Before an official Figma MCP server existed, AI coding agents often had to guess design specs from screenshots — leading to inaccuracies in spacing, colors, or component names. The Figma MCP server solves this by delivering structured design data directly from the Figma file: exact variable values, component names, and layout information instead of visual guesswork. For teams with an established design system, this is particularly valuable because generated code is more likely to match the components and tokens actually in use, rather than inventing new, inconsistent values.

Remote and Desktop Server

Figma recommends the remote server. It connects directly to the hosted endpoint without the desktop app and offers the widest range of features. The desktop server runs locally and is intended for specific organization and enterprise needs. It is also the only option for Figma for Government, currently with limitations. Besides reading designs, agents can, according to the documentation, create and modify native Figma content directly from the MCP client, such as frames, components, variables and auto layout. Code can also be generated from selected frames, and Code Connect links designs to real components in code. Only MCP clients listed in the Figma MCP Catalog can connect.

Who the server fits

Development teams that work closely with designers and regularly turn Figma designs into code benefit the most: the server noticeably shortens the path from design approval to first code implementation. It's also well suited for automatically generating architecture or database diagrams in FigJam from existing code. For occasional design review without a coding angle, the setup effort is less worthwhile, especially given the plan requirements for a practical usage quota.

In short: without a sufficient Figma plan, the server remains a demo-level feature with only a handful of calls per month; only with a Dev or Full seat on a paid plan does it become a practical, everyday tool for design-to-code workflows.

Requirements

A Figma account with a paid plan (Professional, Organization, or Enterprise) and a Dev or Full seat for a practical usage quota; a Starter plan or a View/Collab seat works technically but is limited to a handful of calls per month. Additionally, an MCP client from the Figma MCP Catalog (e.g. Claude Code, Cursor, VS Code, Xcode).

Installation instructions

The Figma MCP server brings design context from Figma files into AI coding workflows. Setup uses OAuth, but the practical benefit depends heavily on your own Figma plan.

Step 1: First: check your Figma plan

The server itself has no extra fee, but without a paid Figma plan with a Dev or Full seat, only a handful of calls per month are possible (Starter plan: up to 20/month, View/Collab seat on a paid plan: up to 6/month). For regular use, at least a Dev or Full seat on a Professional, Organization, or Enterprise plan is needed.

Step 2: Setting up in Claude Code

The recommended way is the official Figma plugin, which includes MCP settings and matching agent skills:

bash
claude plugin install figma@claude-plugins-official

Alternatively, set it up manually:

bash
claude mcp add --transport http figma https://mcp.figma.com/mcp

Adding --scope user makes the server available in all projects instead of only the current one. Then run /mcp in Claude Code, select "figma", choose "Authenticate", and confirm access in the browser window that opens.

Setting up in other clients

Figma also documents setup for Codex, Cursor, VS Code, and Xcode; the details differ by client, but the underlying mechanism (remote server over HTTP, OAuth sign-in) stays the same.

Using write access deliberately

With the right skills, the agent can not only read but also directly create or modify frames, components, and variables in Figma Design files, and edit FigJam boards. Since the server operates with the signed-in account's permissions, it's advisable to try new write workflows on a test file first before running them against production design systems.

Step 3: Verifying the setup

After signing in, run the whoami tool (or ask the agent to) to confirm the email address used and the associated Figma plans and seat types. Then test with a harmless, read-only task, such as "Describe the components in this Figma frame."

Common connection issues

If sign-in hangs in the browser window after confirming, a client restart and another attempt via /mcp usually resolves it. If whoami shows the wrong or unexpected Figma plan, it may be because multiple Figma accounts are signed in in the browser — make sure the correct account is active before signing in.

Keeping usage limits in view

Since usage limits vary significantly by Figma plan and seat type, it's worth checking the current limits in the Figma account before heavier use. If the monthly or daily quota is reached, the server reports this via an error that can only be resolved by waiting for the next window or upgrading the plan.

Source: developers.figma.com/docs/figma-mcp-server/ (Introduction, Remote server installation, Rate limits & access), checked on 2026-09-06.

claude mcp add --transport http figma https://mcp.figma.com/mcp

Authentication

OAuth sign-in to your own Figma account, triggered from the MCP client. For organizations, enterprise-managed authorization via Okta Cross App Access (XAA) is additionally supported, currently only for Claude.

Required access permissions

The agent can only access Figma content the signed-in account already has view or edit permissions for. Usage limits depend on plan and seat type (see cost details); write tools such as creating new files are exempt from the read rate limits.

Transmitted or stored data

Requests go to Figma-hosted infrastructure at mcp.figma.com. Responses contain design data from accessible Figma files (layout, components, variables, sometimes images) and are passed to the MCP client and its language model. Write tools directly modify content in the connected Figma or FigJam files.

Security risks

Since the server operates with the permissions of the signed-in Figma account, a misdirected agent with write access can accidentally modify or overwrite design files. Design files can contain confidential product information that reaches the agent's language model. For production design systems, it is advisable to try write access on test files first and use accounts with the narrowest possible file access for automated workflows.

License and costs

License
Not recorded yet.
Cost
paid

The MCP server itself does not incur separate costs but is tied to a paid Figma plan with a Dev or Full seat for a practical usage quota (Starter plan or View/Collab seat: only a few calls per month). Figma's regular plan and seat pricing applies independently of the MCP server.

Alternatives

Not recorded yet.

At a glance

Provider
Figma
Status
Official server
Deployment
Remote
Current version
Not recorded yet.
GitHub stars
1,965
Last reviewed
07.09.2026

Repository and documentation

Categories

Supported clients