OpenFigma MCP

Stop your AI agent from burning 350k tokens on a single Figma screen. OpenFigma returns a deduplicated, simplified design — typically 3–4× smaller than the raw API JSON — then turns it into tokens, code for 8 frameworks, and accessibility/diff/drift reports. All on a free Figma Personal Access Token. No paid Dev Mode seat.

The most capable free Model Context Protocol (MCP) server for Figma. It connects your designs to AI coding assistants (Lovable, Cursor, VS Code, Claude, Gemini) without a paid Figma Dev Mode seat — using a free Personal Access Token against the Figma REST API.

It is a drop-in superset of Framelink's figma-developer-mcp (same get_figma_data, simplified output, CLI fetch, config flags) and then goes well beyond every free and paid competitor.

✨ What makes it stand out

OpenFigma is the only free Figma MCP that does all of these — several of which no Figma MCP at any price offers:

📊 See COMPARISON.md for a full, honest feature-by-feature breakdown vs. the official Figma Dev Mode MCP — including the one thing only Figma's first-party server can do (write to the canvas).

Related MCP server: figmind

🚀 Core features

1. Free-account friendly — PAT or OAuth Bearer token; no paid Dev Mode seat.

2. Simplified design data — get_figma_data keeps only what matters (layout, fills, strokes, effects, text, radius, opacity, bbox), converts autolayout → flexbox, colors → hex, and deduplicates styles into a globalVars block. ~3–4× smaller than raw API JSON; far smaller on style-heavy files. Untrusted Figma text is scanned for prompt injection and flagged.

3. Design → tokens → code, in one server — extract a full design-token system, export it to 8 formats, generate typed components for 8 framework targets (React-Tailwind, React-inline, Vue, Svelte, Angular, HTML/CSS, Flutter, SwiftUI), and pull real inline-SVG icons.

4. Quality + safety tooling — WCAG contrast audit, version diffing, and design-vs-code drift detection.

5. Three output formats — yaml (default), json, or tree.

6. CLI — fetch, tokens, codegen, audit subcommands print straight to stdout.

7. Auto-routing assets + rules writer — downloads images into the right figma-export/ folder and keeps LOVABLE.md / .cursorrules current; serves assets over localhost in HTTP mode.

8. Dual transport + multi-tenant — HTTP/SSE (Lovable, default port 3845) or stdio; per-request X-Figma-Token header for shared deployments.

9. Honesty layer — when the Figma plugin isn't connected, canvas-write tools return a structured supported:false instead of fabricating success. A capabilities tool reports exactly what will work (including live plugin status).

10. Real canvas writes — a free companion Figma plugin + WebSocket bridge lets agents create/edit frames, text, rectangles, fills, and more — the one thing the REST API alone can't do. See figma-plugin/.

🛠️ Installation & Usage

🖥️ Desktop app (no terminal required)

Prefer a UI? OpenFigma ships a stunning cross-platform desktop app (Electron + React) that runs the server, explores designs, extracts tokens, and generates code — all visually. See desktop/.

cd desktop && npm install && npm run dev     # or build an installer: npm run dist

One-command (npx)

npx open-figma-mcp --figma-api-key figd_YOUR_TOKEN --stdio

Local clone

npm install
node src/server.js --figma-api-key figd_YOUR_TOKEN          # HTTP/SSE on :3845
node src/server.js --figma-api-key figd_YOUR_TOKEN --stdio  # stdio for editors

⌨️ CLI fetch

Print simplified design data and exit — same pipeline as the get_figma_data tool.

# YAML (default)
node src/server.js fetch "https://figma.com/design/ABC123/My-File?node-id=12-822" --figma-api-key figd_x

# JSON, piped into jq
node src/server.js fetch "https://figma.com/design/ABC123/My-File?node-id=12-822" --figma-api-key figd_x --format=json | jq '.nodes[0]'

# Experimental compact tree
node src/server.js fetch "https://figma.com/design/ABC123/My-File?node-id=12-822" --figma-api-key figd_x --format=tree

# Explicit flags instead of a URL, with a depth cap
node src/server.js fetch --file-key ABC123 --node-id 12:822 --depth 3 --figma-api-key figd_x

Wrap URLs in quotes — characters like & and ? break unquoted in most shells.

fetch flags: --file-key, --node-id, --depth, --format, --json, --figma-api-key, --figma-oauth-token, --env. Explicit flags override values parsed from the URL.

More CLI subcommands

# Export design tokens (css/scss/tailwind/tailwind4/js/ts/json/style-dictionary)
node src/server.js tokens "https://figma.com/design/ABC123/..." --figma-api-key figd_x --format=tailwind4 > theme.css

# Generate component code from a node
node src/server.js codegen "https://figma.com/design/ABC123/...?node-id=12-822" --figma-api-key figd_x --framework=vue

# WCAG accessibility audit (JSON)
node src/server.js audit "https://figma.com/design/ABC123/..." --figma-api-key figd_x --page-background "#0b0b0b"

⚙️ Configuration

All options can be set via CLI flag or environment variable. Precedence: CLI args > environment > defaults. (A per-request X-Figma-Token header overrides everything for that one request.)

Lovable note: 3845 is the port the official Figma Dev Mode MCP uses, so it's a sensible default. Add OpenFigma to Lovable via Custom MCP (not the built-in "Figma desktop" tile, which is reserved for the official Figma app). For drop-in compatibility with figma-developer-mcp configs that assume 3333, set FRAMELINK_PORT=3333 or --port=3333.

Authentication

• Personal Access Token (recommended): generate under Figma → Settings → Security → Personal access tokens with File content: Read and Dev resources: Read scopes.

• OAuth Bearer token: pass --figma-oauth-token / FIGMA_OAUTH_TOKEN; the server then sends Authorization: Bearer instead of X-Figma-Token. OAuth takes precedence over a PAT when both are set.

• Per-request (HTTP mode): send X-Figma-Token: figd_xxxx on each request to override the server's configured credentials for that request only — ideal for centrally hosted, multi-user deployments.

Network proxy

Behind a corporate proxy? Set --proxy=http://proxy:8080 (or FIGMA_PROXY). The server also respects the standard HTTP_PROXY / HTTPS_PROXY / NO_PROXY variables automatically. Use --proxy=none to ignore inherited proxy env vars and connect directly.

🤖 MCP Client Setup

Lovable Desktop

Lovable's built-in "Figma desktop" connector is reserved for the official Figma desktop app's Dev Mode MCP — it can't be enabled by a third-party server. To use OpenFigma in Lovable, add it as a Custom MCP ("Connect your own local MCP"):

1. Start OpenFigma in HTTP mode (node src/server.js → :3845), or use the desktop app's MCP Server → Start.

2. In Lovable: Resources → Connectors → Custom MCP → HTTP.

3. Point it at the Streamable HTTP endpoint: http://127.0.0.1:3845/mcp.

OpenFigma serves the modern Streamable HTTP transport at /mcp (what Lovable and recent Cursor/Claude expect) and the legacy SSE transport at /sse for older clients. Always prefer /mcp.

Cursor / VS Code / Claude Desktop

{
  "mcpServers": {
    "open-figma-mcp": {
      "command": "node",
      "args": ["C:/path/to/open-figma-mcp/src/server.js", "--stdio"],
      "env": { "FIGMA_API_KEY": "figd_YOUR_TOKEN" }
    }
  }
}

HTTP / SSE

{
  "mcpServers": {
    "open-figma-mcp": {
      "url": "http://localhost:3845/mcp"
    }
  }
}

/mcp is the modern Streamable HTTP endpoint (recommended). /sse is still served for legacy SSE clients.

🧰 Tools

Read & simplify

• get_figma_data — fetch + simplify a file or nodeIds (with depth), in yaml/json/tree. Start here.

• get_metadata / get_design_context — lighter structural views.

• get_variable_defs — variables/tokens (falls back to document styles on free accounts).

• get_figjam, get_libraries, search_design_system, whoami.

Design → code

• get_design_tokens — extract a token system, export as css/scss/tailwind/tailwind4/js/ts/json (W3C)/style-dictionary.

• generate_code — component code in react-tailwind, react-inline, vue, svelte, angular, html, flutter, or swiftui (responsive via constraints). Also available as get_code (official Figma MCP tool-name alias).

• generate_component_api — typed TS interface / Vue defineProps from component properties & variants.

• create_design_system_rules — generate a rules file from the design's real tokens so generated code matches the design system (parity with the official Figma MCP tool).

• extract_vectors — real inline SVG icons from path geometry (themeable currentColor).

Quality & review

• audit_accessibility — WCAG contrast + tap-target audit.

• get_design_diff — semantic diff between two file versions (added/removed/changed nodes).

• audit_drift — design tokens vs. your repo's colors (missing / stale / near-miss).

Figma API coverage

• get_comments / add_comment, get_versions, get_image_fills, get_dev_resources, get_projects.

• download_figma_images / download_assets / get_screenshot (disabled by --skip-image-downloads).

Meta

• capabilities — what this server can and cannot really do (including live Figma-plugin status).

• Code Connect toolchain (get_code_connect_map, get_code_connect_suggestions, …).

Canvas read/write (live when the OpenFigma Figma plugin is connected)

• get_canvas_selection, get_canvas_document, get_node_info — read live selection / document / node.

• create_frame, create_rectangle, create_ellipse, create_text — add nodes.

• create_component_from_node, create_instance, group_nodes — components & structure.

• set_fill_color, set_stroke_color, set_corner_radius, set_opacity, add_drop_shadow, set_image_fill — styling.

• set_text, set_name, set_auto_layout, move_node, resize_node, clone_node, delete_node — edit.

• When the plugin isn't connected these return an honest supported:false. File-level ops (create_new_file, HTML→canvas, Mermaid→FigJam) remain out of scope.

✅ Testing

npm run test:unit          # offline, deterministic (serializers, simplify, config, proxy, URL parsing)
npm run test:integration   # spins up the server over stdio + exercises the CLI fetch
npm test                   # both

The unit tests run with no network and no token; the simplification tests use a cached fixture when present.

🤝 Project & community

• Contributing guide — dev setup, how to add a framework or token format

• Architecture & working mechanism — how OpenFigma and the official Figma MCP work, with diagrams

• Deployment guide — stdio, HTTP, Docker, cloud platforms

• Changelog — what changed, version by version

• Security policy — how to report issues, and the localhost/auth notes

• Code of Conduct

• Launch & market-research notes — positioning and roadmap

Issues and PRs are welcome. Good first issues are labeled. If OpenFigma saved you tokens, a ⭐ helps others find it.

📄 License

MIT License. Feel free to share and modify!