Figma MCP in Cursor
If you use Cursor, Figma’s own MCP server is the supported route, and it works with Cursor. FigmaMCP does not name Cursor as a supported client: it is built for Claude Code and Codex. We say so plainly so you can pick the right tool.
Which option fits
| You use | Start with |
|---|---|
| Cursor, and you mostly read designs to write code | Figma’s official MCP server |
| Cursor, and you want an agent to edit the canvas | Talk to Figma MCP, whose README names Cursor |
| Claude Code or Codex on a Mac, and you want edits with no call quota | FigmaMCP |
What FigmaMCP supports
FigmaMCP connects two agents automatically: Claude Code and Codex. The Mac app checks for both, installs the plugin in Figma and registers the FigmaMCP tools with each agent it finds. Cursor is not in that list. We have not tested FigmaMCP with Cursor, so we do not claim support for it.
What the FigmaMCP README says about other clients
The FigmaMCP README has a section for other MCP clients. It says that any client that can launch a local MCP server can be given a FigmaMCP entry in its MCP config, and it names Cursor’s config file, ~/.cursor/mcp.json, as an example. It then says to install the Mac app so the plugin is registered in Figma. That is the documented path. It is a manual one, and the project does not list Cursor as tested or supported.
A limit to check first
FigmaMCP registers 46 tools. Each tool adds its name and parameter schema to the agent’s context. The FigmaMCP contributor guide notes that some MCP hosts, Cursor among them, have shown a cap on the total number of tools, in the range of 40 to 128 depending on host and model. We have not measured this in Cursor. If you try a manual setup, check how many tools your client loads.
What stays the same either way
- FigmaMCP needs macOS and the Figma desktop app. It does not run in the browser.
- Edits happen only where the plugin’s AI can edit this file switch is on.
- Each edit names its target layer, and the name must match.
- Failures return structured errors, such as
READ_ONLY_MODEorPLUGIN_PEER_UNAVAILABLE.
Cursor and Claude Code side by side
Using Claude Code or Codex next to Cursor is fine: they can run in a terminal beside it, and both reach the same open Figma file. You can read and write code in Cursor while your terminal agent edits the design through FigmaMCP. Do not point two tools at the same file at once, because two agents can change the same layers.
Download for Mac Version 0.1.20 macOS 14+ · Intel & Apple Silicon · ~155 MB
Related: Compare Figma MCP options · Integrations · Figma MCP alternative
Questions
Does FigmaMCP work with Cursor?
Which Figma MCP server works with Cursor?
Can I add FigmaMCP to Cursor by hand?
Can I use Cursor and Claude Code together?
Last updated: