Analysis

Figma MCP in Cursor

Use Model Context Protocol to connect Cursor to Figma when drafting user stories: setup pattern, credentials, security, and troubleshooting.

Purpose

Model Context Protocol (MCP) lets an AI assistant in Cursor read Figma files, frames, or design context while you describe or refine work. That matches well with the User story layout and Jira user story skill: you can reference what is in the design without pasting large exports or screenshots for every detail.

The exact MCP server depends on Figma’s current API and which server implementation you use. This page describes how to wire a server safely in Cursor; it does not pin a single third-party package.

Prerequisites

  • A Figma account with access to the files or teams you need.
  • Credentials as required by your MCP server: often a Personal Access Token from Figma Settings → Security (or OAuth, if the server supports it). See Figma’s developer documentation for API access and token scopes.
  • Cursor with MCP support enabled (see Cursor MCP documentation).

Cursor MCP basics

  1. Open Cursor Settings and find MCP, or edit your MCP config as described in the Cursor MCP docs.
  2. Add a server entry:
    • Command and args as documented by the Figma MCP server you choose.
    • Environment variables: typically FIGMA_* or names the server documents (e.g. token, optional file or team id). Use environment or Cursor’s secret storage; never commit secrets to git.

Server-specific setup

  1. Pick an MCP server that talks to the Figma REST API (or the integration model your org standardises on).
  2. Create a Figma access token with the minimum scope needed for your workflow; paste it only into env or Cursor secrets.
  3. Confirm your file and team permissions in Figma: the token must be able to read the files you reference.

Security

  • Never commit Figma tokens, .env files with tokens, or mcp.json containing secrets.
  • Rotate tokens if they are exposed or when people leave the team.
  • Prefer read-only or minimal scopes if the server allows it; only grant what story drafting needs.

Troubleshooting

SymptomWhat to check
Connection errorsNetwork, VPN, and that the MCP process can reach api.figma.com (or your org’s endpoint).
403 / 404 on fileFile key or URL wrong, or your account cannot access that file.
Stale or missing nodesNode id format, file version, or server cache; refresh or re-open the file in Figma.

Related

Jira MCP in Cursor

Use Model Context Protocol to connect Cursor to Jira when drafting user stories: setup pattern, credentials, security, and troubleshooting.

Copyright © 2026