为MCP客户端、终端和代码生成工作流程提供具备配额意识、唯读的Figma工具。

figma-mcp-free 提供了两个显式的读取路径：

1. 一个速率感知的 Figma REST 后端，用于文件、节点、组件、令牌和无头自动化;
2. 经过认证、仅回环的 Figma 开发插件桥，用于用户批准的当前选择捕获，无需 PAT 或 REST 请求。

两条路径都提供相同的有界检查和React、Vue、Svelte或HTML入门代码生成流水线。两条路径都不写入Figma。

能力矩阵

本项目并不取代 Figma 开发模式或官方 Figma MCP 服务器。

figma-mcp-free

Quota-aware, read-only Figma tooling for MCP clients, terminals, and code-generation workflows.

figma-mcp-free provides two explicit read paths:

1. a rate-aware Figma REST backend for files, nodes, components, tokens, and headless automation;
2. an authenticated, loopback-only Figma development-plugin bridge for a user-approved capture of the current selection without a PAT or REST request.

Both paths feed the same bounded inspection and React, Vue, Svelte, or HTML starter-code generation pipeline. Neither path writes to Figma.

Capability Matrix

This project does not replace Figma Dev Mode or the official Figma MCP server. It provides a transparent open-source read pipeline with explicit limits.

Why This Project Exists

Figma REST API limits depend on endpoint, seat, plan, and resource location. This project treats network requests as a budgeted resource:

• node IDs are de-duplicated and batched;
• identical in-flight reads are joined;
• successful responses use a bounded, short-lived memory cache;
• a hard per-client request budget is available;
• short-lived failures retry within configured ceilings;
• long-lived or plan-related 429 responses fail fast with structured metadata;
• response size can be bounded by depth or transformed into compact selection context;
• the local Plugin bridge can capture the current selection without spending REST quota.

See Figma’s official REST API rate-limit documentation for current limits. Figma may change them.

Features

• MCP STDIO server with stable, read-only tools.
• CLI for REST inspection, batch node reads, component search, token export, and code generation.
• Local bridge CLI for serving, listing, inspecting, generating from, and clearing the captured selection.
• Figma development plugin using JSON_REST_V1 after an explicit Capture & Send action.
• Full /file and /design URL parsing with numeric node-id=1-2 normalization to 1:2.
• Bounded implementation context through inspect_selection and inspect_current_selection.
• W3C-style design tokens for colors, sizes, spacing, typography, and shadows.