How to Connect Cursor to Figma with MCP

Connecting Cursor to Figma's MCP server lets Cursor's agent read your designs and turn them into code that matches them. With the remote server, it can also write to the Figma canvas, such as creating frames or diagrams.

Checked against: Figma's remote server setup guide and Cursor's MCP docs on 28 October 2026. eSEOspace did not run these steps; menus can change, so follow the vendor's page if it differs.

Before you start

You need:

• Cursor installed on your computer.
• A Figma account with access to the files you want to use. Figma says you can only use the server with files you already have access to.
• A suitable seat. Figma's rate limits page lists up to 20 tool calls a month for View and Collab seats on every plan. Full and Dev seats get up to 200 a day on Professional and Organization, and up to 600 a day on Enterprise.

You do not need the Figma desktop app. Figma says the remote server connects directly to Figma.

Steps

Option 1: Install the Figma plugin (recommended)

Figma's guide gives these steps:

1. Open the command palette (Cmd Shift P on Mac, Ctrl Shift P on Windows).
2. Search for Open chat.
3. In the chat, enter this command and click Submit:

/add-plugin figma

1. Click Add Plugin. You can also install it from the Figma plugin page in the Cursor Marketplace.
2. Open the command palette again, search for Cursor Settings and select Tools & MCP.
3. Under Installed MCP Servers, click Connect next to Figma.
4. When prompted, click Allow access to let Cursor access your Figma account.

Option 2: Add the server by hand

If you can't install plugins, Figma offers an Add the Figma MCP server to Cursor link that opens Cursor's install prompt. Click Install, then Connect, Open and Allow access.

If the link doesn't open Cursor, add this configuration yourself. Figma's guide gives it as:

{
  "mcpServers": {
    "figma": {
      "url": "https://mcp.figma.com/mcp"
    }
  }
}

Cursor's docs say to put it in .cursor/mcp.json in your project, or in ~/.cursor/mcp.json to use it in every project. Save the file, then click Connect next to Figma to sign in.

The manual route skips Figma's skills and rules. Figma says you can add the skills separately.

A note on menus: Figma's guide points to Cursor Settings, Tools & MCP. Cursor's own docs now say you enable and disable servers from Customize in the sidebar. Use whichever your version shows.

Check that it works

In Figma, right-click a frame or layer and select Copy link to selection. Paste that link into your prompt. Figma says the client won't open the link; it pulls out the node ID the server needs.

Example prompts:

• "Help me implement this design: [paste link to selection]." Figma's design-to-code tools, such as get_design_context, return the design context.
• "Create a flowchart for the user authentication flow using the Figma MCP generate_diagram tool." This prompt comes from Figma's guide.
• "Run whoami and tell me which Figma account and seat I'm using." Figma suggests whoami for checking access problems.

Cursor shows each tool call in chat, with expandable arguments and responses, so you can confirm Figma's tools ran.

Permissions and safety

The Figma server is no longer a read-only design source. The Figma MCP server profile lists write tools such as use_figma, create_new_file and generate_figma_design.

• Approve each call. Cursor asks for approval before using MCP tools by default. Keep that on for shared files. Our guide to permissions and approvals explains why.
• File access follows your account. The server can reach the files your Figma account can reach, and no more.
• Credits. Figma says generate_image uses Figma AI credits, and Weave tools use Weave credits.
• Team controls. Cursor's enterprise admins can allowlist approved MCP servers and limit which tools run automatically.

Design files can hold text written by other people, which an agent may treat as instructions. Read about prompt injection through tool results and see the MCP Security Center.

If it doesn't work

• The plugin command fails. Use the manual route above.
• Rate limited. Figma's fix is a seat or plan upgrade. Its limits apply to tools that read data from Figma; some write tools are exempt.
• Permission errors. Figma says to check the link points to a Figma Design, FigJam or Figma Make file. Then check which account you're signed in with (whoami) and that it belongs to the plan that owns the file.
• Server errors in Cursor. Cursor's docs say to open the Output panel (Cmd+Shift+U) and select "MCP Logs" to see connection, sign-in and crash errors.

Next step

Once Figma is connected, try one small component before a full page. For the full tool list and seat rules, read the Figma MCP server profile. For other editors and apps, browse the MCP connection guides, or see how Claude Code connects to Figma.

Frequently asked questions