Figma-to-Cursor workflow uses MCP servers as bridge between design and code

Source type	Community
Confidence	Low
Last verified	2026-03-22
Topics	figma-workflows toolchain

Insight: According to Xinran Ma, the Figma-to-Cursor workflow uses Model Context Protocol (MCP) servers as a bridge, with two implementation paths: a remote MCP server connecting directly to Figma files in the browser, and a desktop MCP server using the Figma desktop application at localhost:3845. The remote approach requires copying frame links from Dev Mode; the desktop approach reads context from currently selected frames automatically.

Detail: Prerequisites: Cursor (Pro plan recommended for token usage), Figma Professional with Dev seat ($12+) for Dev Mode access, and optionally a Gemini API key. Remote setup: users paste a special URL into their browser to install Figma MCP directly in Cursor settings. Desktop setup: manually add MCP server configuration with endpoint http://127.0.0.1:3845/mcp. Verification step: use a simple prompt like "Read the name of this frame: [link]" to confirm connectivity before attempting complex tasks.

Sources

• Xinran Ma / Design with AI — "How to set up the Figma → Cursor workflow" (2026-03-04)

Related: figma-native-slots-repeating-items