Design & Tools
5 min read

Figma MCP Allowlist: How to Approve Claude Code and Cursor Without Breaking Active Work

Colorful toy brick cars wait in front of a barrier, while two already stand on a raised platform
Image: AI-generated
In short

Since November 17, 2026, admins on Figma Organization and Enterprise plans can decide which OAuth apps and MCP clients, such as Claude Code or Cursor, can access company files. Switching to approved apps only also cuts off existing connections. So approve the apps your team uses first, then flip the switch.

What did Figma change on November 17?

Organization admins now get an allowlist for apps that connect to Figma via OAuth. OAuth is the sign-in method that lets you grant an app access without handing over your password. MCP clients like Claude Code and Cursor are explicitly included. MCP (Model Context Protocol) is the standard AI agents use to read and operate tools like Figma. According to the release note from November 17, a new Extensions tab appears in the admin area for this. The feature is only available on Organization and Enterprise plans and is rolling out gradually. If you don't see it yet, it should arrive in the coming days.

This matters because AI agents no longer just read. Through the remote Figma MCP server, they can also write to the canvas. Outside your own drafts, that requires a Full seat according to the Figma documentation. It's free during the beta and will later become a usage-based paid feature. For how this works with images and video through Weave, see our article on Figma Weave MCP.

Which two allowlists exist now?

There are two layers, and forum threads mix them up all the time. Figma itself only lets clients from its own catalog connect to the remote server: per the installation guide, only clients listed in the Figma MCP catalog can connect. The new allowlist sits one layer below that and belongs to your organization.

Figma MCP catalog Your organization's allowlist
Who decides Figma Your organization's admin
Applies to All Figma accounts Your organization's files and resources
Plans All plans with MCP access Organization and Enterprise
Typical question "Can my tool connect to Figma at all?" "Can it access our files?"

A client has to clear both hurdles. If a tool isn't in the catalog, your own approval won't help.

What happens when you switch to approved apps only?

Existing connections lose access unless the app is on the list. The Figma help article says so directly: apps that aren't on the allowlist lose access to your organization's resources, even if team members authorized them long ago. The details:

  • Default: "Allow all apps" means any app can connect without approval. You'll find the switch to "Only admin-approved apps" under Admin, Extensions, Apps, Settings.
  • Approval covers permissions: You approve an app with the permissions it requests, such as reading files or writing comments. If it later asks for more, like write access, you need to approve it again. If you decline, the old permissions stay in place.
  • Everyone still signs in individually: Approval doesn't replace each person's own authorization.
  • Requests: Optionally, members can request an app. You'll see requests under Admin, Dashboard, All requests, along with the reason. Declining a request doesn't block future requests.
  • Revoking: If you revoke approval, all users lose access on their next request. Switch back to allowing all apps and blocked connections work again. If the sign-in has expired in the meantime, people need to reconnect.

Where are the gaps?

The help article doesn't cover two access paths, and those are exactly the ones you should know about.

  1. The desktop MCP server. Besides the remote server, there's a local server that runs through the Figma desktop app. According to the setup guide, you enable it in Dev Mode, and it then responds at 127.0.0.1:3845 on your own machine. Figma doesn't say whether the allowlist covers it.
  2. Personal access tokens. Personal keys for the Figma API, which many scripts and automations rely on, aren't mentioned in the article either.

Our take: Don't assume the allowlist covers everything. Test both paths with a test account before you announce internally that AI access is now under control. One more setting belongs on your list: since November 3, cloning connected GitHub repositories is on by default for new connections, according to the release notes. Admins can turn it off per repository.

What does this mean for your team?

Make the switch, but in this order:

  1. Take inventory: Ask your team which AI tools are connected to Figma. The Suggested section in the Apps tab recommends apps to approve.
  2. Approve first, then switch: Put Claude Code, Cursor and everything else in production use on the list beforehand. Otherwise your design-to-code pipeline stops in the middle of a sprint.
  3. Allow requests: Keep "Allow plan members to request apps" checked. That way a new tool gets requested instead of quietly worked around.
  4. Grant permissions deliberately: Reading is different from writing to the canvas. After the beta, writing costs money.
  5. Plan for limits: According to Figma, a Full or Dev seat on the Organization plan gets 200 tool calls per day (15 per minute), and on the Enterprise plan 600 per day (20 per minute). View and Collab seats get only 20 calls per month on every plan. Figma reserves the right to change these limits.

Agencies and freelancers face one more issue that few people have on their radar. Our take: if you work with your AI agent inside a client's Figma organization, their admin decides whether you get access. Before the project starts, confirm that your client is approved, or your connection will break the moment the client switches. For a similar way to keep AI agents on a leash in your website, see our post on the Webflow MCP server. If you want to connect design and code with agents, we can help you set it up.

Frequently asked questions

Is the Figma allowlist available on the Professional plan?

No. According to Figma, it's only available on Organization and Enterprise plans, and only organization admins can configure it.

How do I approve an app that isn't listed in the Figma Community?

Use Add app in the Apps tab. Paste the Community URL or the client ID, which you get from the vendor's documentation.

Does revoking approval delete my team members' sign-ins?

No. Individual authorizations stay in place; the organization policy only blocks access to your resources. If you approve the app again, it works again as long as the sign-in hasn't expired.

Can I approve any AI agent I want?

Only partly. For the remote MCP server, Figma only allows clients from its MCP catalog. If a client isn't listed there, your own allowlist can't connect it either.

Sources

  1. Figma: Release Notes, Manage an allowlist of approved OAuth apps, including MCP clients
  2. Figma Help Center: Manage OAuth apps and MCP clients
  3. Figma Developer Docs: Figma MCP server
  4. Figma Developer Docs: Plans, access and rate limits
This article was created with AI.
Got a project in mind?

Tell us what you're planning. You'll get an honest assessment within 24 hours.

Got it! We will get back to you asap!
Whoopsie! Something went totally wrong here... Maybe just send an email to hi@blocksandcolors.de? Sorry!
Or email me directly: hi@blocksandcolors.de