FigmaMCP

FigmaMCP plugin not showing in Figma

FigmaMCP is not on Figma Community, so searching there finds nothing. After the Mac app installs it, FigmaMCP appears under Plugins › Development › FigmaMCP in the Figma desktop app. If that menu is empty, check the app, the install and Figma itself, in this order.

Where the FigmaMCP plugin lives

FigmaMCP runs as a development plugin, not a Community plugin. The Mac app adds it to Figma’s plugin list. You then open it from the Plugins menu, then Development, then FigmaMCP, in a design file. The Figma desktop app is required. A development plugin does not run in the browser.

Check in this order

Plugin not showing: symptom and what to do
SymptomWhat to do
Searched Figma CommunityFigmaMCP is not there. Open Plugins, Development, FigmaMCP in a design file.
Using Figma in the browserUse the desktop app. A development plugin does not run in the browser.
Development menu is emptyOpen the FigmaMCP Mac app, click Add to Figma, then reopen the file.
You installed while Figma was runningLet Figma restart. The plugin appears when Figma starts again.
Plugin opens but the agent cannot see itThe agent may return PLUGIN_PEER_UNAVAILABLE. Open the plugin in the file you want edited, then retry. See Figma MCP not working.
The plugin is open in two Figma tabsThe second copy is refused (PLUGIN_PEER_AMBIGUOUS) and the message shows in the plugin panel. Close or disconnect the duplicate and leave one open.

What the Mac app installs

The FigmaMCP Mac app registers the plugin for you. It adds the FigmaMCP development plugin to Figma’s settings.json in ~/Library/Application Support/Figma, and it saves the original as settings.json.figmamcp-backup next to it. It writes this while Figma is closed. If Figma was running and the plugin was missing, the app restarts Figma once. The setup page lists every other file the installer writes.

If you did not allow Accessibility

FigmaMCP can open the plugin for your agent if you allow Accessibility. Without that permission, you open the plugin yourself once in each file (Plugins, Development, FigmaMCP) and leave it open while your agent edits. Each file needs its own open plugin, and the agent can only reach files where it is open.

Remove and re-add the plugin

To reset a plugin that does not behave, choose Plugins, Development, Manage plugins in development in Figma, and remove FigmaMCP. Then open the FigmaMCP Mac app and click Add to Figma again. This changes only the plugin entry. If you want a full uninstall, follow the steps on the setup page.

Related: Setup · Not working · How it works · Troubleshooting hub

Questions

Why is it not on Figma Community?
It runs as a development plugin installed by the Mac app. It is not listed there.
Do I need to open it in every file?
Without Accessibility permission, yes: open it once per file and keep it open while the agent edits.
Can I use the plugin in Figma in the browser?
No. A development plugin needs the Figma desktop app.
Will adding the plugin change my Figma settings?
The app adds the plugin to Figma’s settings.json and keeps the original as settings.json.figmamcp-backup.

Last updated: