Figma MCP shows "Forbidden" in Automations / Cloud Agents

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Adding the official Figma MCP (https://mcp.figma.com/mcp) in an Automation’s Tools tab immediately shows a red “Forbidden” badge. No browser redirect to Figma ever opens, so the OAuth flow fails before authorization. The button shows “Disconnect” even though no grant was created. Headers / Client ID / Client Secret are blank (as expected for the official server). Uninstalling/reinstalling the Figma plugin from the org changes nothing.

Figma only allows allowlisted MCP clients. Could it be that the Cursor Cloud agents MCP client is not approved by them yet?

Steps to Reproduce

  1. Add the Figma plugin from the Cursor marketplace in your organization
  2. Create an automation at cursor.com/automations
  3. Tools tab → Add Figma
  4. Badge immediately shows “Forbidden”; no OAuth screen appears

Screenshots / Screen Recordings

Screenshot 2026-06-10 at 18.31.07.png
Screenshot 2026-06-10 at 18.31.07.png1822×118 7.11 KB

Operating System

MacOS

Version Information

Cursor Automations

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hi @mattioli_trmd Thanks for the post! Figma MCP is not supported in Cloud agents right now (including cloud agent automations). Figma MCP is fully supported in the IDE and the CLI, however.

7

Hi @kevinn! Are there any plans to support it? If so, is there any estimated timeline? Thanks!

8

Don’t have an estimated timeline! We would like to support it absolutely but it is a joint effort with the Figma team

9

@kevinn ok, thanks for the answer anyway!