Figma MCP server

Figma × Cursor

Use the Figma MCP server
in Cursor

Pull design files, frames, and specs into your AI for build-ready context. This guide connects Figma to Cursor (the AI code editor) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · Note: Figma currently restricts third-party sign-ins — API-key path recommended

Setup: Figma in Cursor

Cursor adds MCP servers via MCP settings or install deep links. The gateway route takes about two minutes:

  1. Connect Figma to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to Cursor' — Cursor opens and asks to install the gateway.
  3. Confirm and approve the sign-in.
  4. Figma's tools are now available to Cursor's agent, governed by your rules.

What to ask once it’s connected

Pull the specs and spacing from this frame.
List the components in our design-system file.
Give me build-ready context for this screen.
What changed in the design since last week?

Why route it through a gateway

One URL, every client

The same Figma connection works in Claude, Claude Code, ChatGPT, VS Code too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool Figma exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything Cursor did with Figma — searchable, exportable, auditable.

Scanned and probed

Figma passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: Figma in Claude · Figma in Claude Code · Figma in ChatGPT · Figma in VS Code