Figma MCP Server: Setup, Write Tools and Security (Oct 2026)

Q: Is "figma mcp" the same as Figma's official server?

Not always. Many guides and repos called "figma mcp" use Framelink (figma-developer-mcp), a popular third-party server that reads Figma files with a personal access token. It is not made by Figma.

On this page

Figma MCP Server: Setup, Write Tools and Security (Oct 2026)

The Figma MCP server is Figma's own official server. It gives an agent design context (layers, variables, screenshots, Code Connect maps) and, on the remote server, can also write to the canvas. TrustedMCP grades it B. The short version: use it, but keep the write tools behind your approval, because one sign-in covers everything.

What it connects

Figma runs two versions:

Remote server at https://mcp.figma.com/mcp. This is Figma's recommended default. You sign in with your Figma account in the browser. It has read tools and write tools.
Desktop server at http://127.0.0.1:3845/mcp. You switch it on inside the Figma desktop app (Dev Mode, then "Enable desktop MCP server"). It needs a Dev or Full seat on a paid plan, and it has no write tools.

Read tools pull design context, variables, screenshots and Code Connect mappings for the file or selection you point at. Write tools (remote only) can create files, upload assets, generate images (using AI credits) and run code the model writes through Figma's Plugin API.

Figma also sets limits: only clients in Figma's MCP catalog can connect, View and Collab seats get 20 uses a month, and Dev and Full seats have daily and per-minute limits by plan.

Setup

These snippets come from Figma's remote server installation guide.

Claude Code:

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

Cursor (Cursor Settings > Tools & MCP):

{ "mcpServers": { "figma": { "url": "https://mcp.figma.com/mcp" } } }

VS Code (mcp.json, via "MCP: Open User Configuration"):

{ "inputs": [], "servers": { "figma": { "url": "https://mcp.figma.com/mcp", "type": "http" } } }

On first use your client opens a Figma sign-in page in the browser. Approve it and you're connected.

For the desktop server, turn it on in the Figma desktop app and point your client at http://127.0.0.1:3845/mcp, following Figma's local server installation guide.

Security notes

One sign-in covers everything. Figma's OAuth offers a single scope, mcp:connect. There is no read-only scope and no way to grant read tools without write tools. Whatever you can edit in Figma, the agent can edit too.

The write tools are powerful. The most powerful one runs model-written code through the Plugin API inside any file you can edit. Others create files and upload assets. Figma doesn't document a way to switch write tools off on the server.

Design files are untrusted input. Layer names, text and comments in a file can be written by anyone with edit access, including people outside your team on shared files. That text goes into the model's context.

How to limit the risk:

For read-only work, use the desktop server. It has no write tools at all. It also runs only on your machine and has no login of its own, so keep the Figma app closed when you aren't using it.
Block write tools in your client when you use the remote server. In Claude Code, add deny rules to your settings for the Figma write tools (for example mcp__figma__use_figma), or simply keep tool approval on and decline writes you didn't ask for.
Point write work at a copy. Our advice: duplicate the file and let the agent work there, then bring changes back by hand.
Watch your seat limits and AI credits. Image generation spends AI credits.

See the 5-minute safety check for the general version of this process.

Why it grades B

Authentication: 18 of 30. OAuth with PKCE is the default, but the single all-or-nothing scope counts as coarse.
Maintenance: 18 of 25. Figma's docs and guide repo are active, but the server is closed source, so we score one band lower.
Known CVEs: 25 of 25. None on record for Figma's official server.
Transport: 20 of 20. The remote server uses HTTPS, and plugin code runs in Figma's environment, not on your machine.

Full breakdown on the Figma MCP listing; the method is in how TrustedMCP scores servers.

Frequently asked questions

Is "figma mcp" the same as Figma's official server?

Not always. Many guides and repos called "figma mcp" use Framelink (figma-developer-mcp), a popular third-party server that reads Figma files with a personal access token. It is not made by Figma.

What about the Figma MCP CVEs?

The CVEs that show up when you search "figma mcp", CVE-2025-53967 and CVE-2025-15061, are in the third-party Framelink server, not Figma's official one. If you use Framelink, check you're on a fixed version. Figma's own server has no CVEs on record.

Is Figma MCP free?

Partly. Any seat can try the remote server, including on the free Starter plan, but View and Collab seats get only 20 tool calls a month. Real daily use needs a Dev or Full seat on a paid plan, and so does the desktop server (Professional, Education, Organization, Government or Enterprise). Writing to the canvas is free while it is in beta; Figma says it will later become a usage-based paid feature. Image generation spends Figma AI credits. Sources: Figma's rate limits and access and write to canvas pages.

What are the Figma MCP rate limits?

Per Figma's rate limits and access page:

Seat	Starter	Professional	Organization	Enterprise
View, Collab	20 / month	20 / month	20 / month	20 / month
Dev, Full	not available	200 / day, 10 / min	200 / day, 15 / min	600 / day, 20 / min

Education plans match Professional. A few tools don't count, such as whoami, create_new_file and add_code_connect_map. AI credits are counted separately. Figma says it may change these limits at any time.

Does Figma have MCP skills?

Yes. Figma publishes skills for its MCP server: reusable instructions that teach your agent a Figma workflow. The main one, figma-use, teaches the basics of writing to Figma. Skills don't add new tools; they only guide how the agent uses the server. You can also write your own (in Claude Code, a SKILL.md file under .claude/skills/<skill-name>/). See Figma's create skills page.

Is there a Figma plugin for Claude Code?

Yes. Figma recommends it over the manual setup because it bundles the MCP server settings and Figma's skills:

claude plugin install figma@claude-plugins-official

Restart Claude Code, open /plugin and sign in to Figma. The plain claude mcp add command above does not install the skills. Source: Figma's remote server installation guide.

Can I make it read-only?

Not on the remote server. Use the desktop server, which has no write tools, or deny the write tools in your client.

Does it use a lot of context?

It depends on what you ask for. Screenshots and full design context for a large frame can be big. Point it at a specific frame or selection rather than a whole file. See why MCP servers eat your context window.

More: MCP security best practices · Developer tools category