Design files and connect the desktop application to agents through official and community MCP servers. For Cursor, 2 routes are explicitly documented by the integration maintainer.
Read design context from Figma using its built-in local MCP server.
Platforms: macOS, Windows
The integration documentation explicitly names this client.
Figma desktop and a Dev or Full seat on an eligible paid or education plan; enable the desktop MCP server.
The desktop server does not write to the canvas; Figma offers a separate remote server.
A community plugin and local server connect agents to the Figma desktop Plugin API.
Platforms: Not documented
The integration documentation explicitly names this client.
Bun 1.1+, Figma desktop, file edit access and the development plugin.
The desktop development plugin and a running local relay are required.
| Integration | Cursor compatibility | Requirements |
|---|---|---|
| Figma desktop MCP | Documented setup Setup guide | Figma desktop and a Dev or Full seat on an eligible paid or education plan; enable the desktop MCP server. |
| Figma Bridge MCP | Documented setup Setup guide | Bun 1.1+, Figma desktop, file edit access and the development plugin. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Cursor and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All Figma integrations