← MCP

Figma MCP ServerFigma MCP Server

Figma

MCPMCP 设计系统Design systems 设计转代码Design-to-code 远程托管Remote-hosted 双形态Two forms 套餐门槛Plan requirements partial lifecycle: active 核验Checked 2026-10-30

Figma 官方 MCP server：把设计系统上下文（组件/变量/Code Connect）喂给编码 agent，还能写画布。三条硬口径：远程 server 是官方推荐形态；只有 MCP catalog 里的客户端能连； beta 免费是暂时的，将来转用量计费。

Figma's official MCP server: design-system context (components/variables/Code Connect) fed to coding agents, plus canvas writes. Three hard facts: the remote server is the officially recommended form; only clients in the Figma MCP catalog can connect; beta-free is temporary — usage-based pricing is coming.

适合与不适合When to use it, when not to

适合：设计系统驱动的前端生成流、设计↔代码双向同步团队。不适合：catalog 外客户端；要永久免费写画布的预算假设。

Fits: design-system-driven frontend generation, design↔code sync teams. Not a fit: clients outside the catalog; budget assumptions of permanently free canvas writes.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21

出品属地Origin: 国外出品foreign-made　Figma, Inc.（美国）。Figma, Inc. (US).
国内使用Direct access: 大陆可直连direct OK　developers.figma.com 直连实测 200（2026-10-21）；mcp.figma.com 端点直连未单独测。developers.figma.com measured 200 direct (2026-10-21); the mcp.figma.com endpoint not individually measured.
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-21 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 它自己不调模型——被 MCP 客户端调用的接口实现。它把 Figma 设计上下文（组件、变量、布局数据、Code Connect 映射）喂给编码 agent，让生成代码贴合真实设计系统。
It calls no model itself — an interface implementation called by MCP clients. It feeds Figma design context (components, variables, layout data, Code Connect mappings) to coding agents so generated code matches the real design system.
运行位置Where it runs: 双形态：官方托管远程（mcp.figma.com/mcp——直抓 405=存在需鉴权，官方推荐）+ 桌面本地 server（127.0.0.1:3845/mcp，需桌面 app+Dev/Full 席位）。官方明写「strongly recommend the remote server」。
Two forms: official hosted remote (mcp.figma.com/mcp — direct fetch 405 = exists but needs auth, officially recommended) + desktop local server (127.0.0.1:3845/mcp, requires the desktop app + a Dev/Full seat). The official docs state "strongly recommend the remote server".
本地文件Local files: 桌面形态可把图片资产下载到项目（Download assets 设置项，官方文档直抓所见）；远程形态返回资产链接。设计数据在 Figma 云端。
In the desktop form it can download image assets into the project (Download assets setting, seen in the directly fetched official docs); the remote form returns asset links. Design data lives in Figma's cloud.
关机后的任务Tasks after shutdown: 远程形态在 Figma 侧；桌面形态随桌面 app 生死。无后台任务语义。
The remote form lives on Figma's side; the desktop form lives and dies with the desktop app. No background-task semantics.
工具与扩展Tools & extensions: 取设计上下文与代码、FigJam/Make 内容读取、Code Connect 映射、写画布（create/update 组件与变量——「write to canvas」，专业及以上套餐）；完整清单以开发者文档为准。
Fetch design context and code, read FigJam/Make content, Code Connect mappings, writing to the canvas (create/update components and variables — "write to canvas", Professional plan or above); the complete inventory follows the developer docs.
上下文与记忆Context & memory: 无 server 侧跨会话记忆——设计状态在 Figma 文件本身；Code Connect 是「设计↔代码」映射层不是记忆。
No server-side cross-session memory — design state lives in the Figma files themselves; Code Connect is a "design↔code" mapping layer, not memory.
权限与限制Permissions & limits: 套餐与席位是硬门槛：远程 server 各套餐可用但写画布要 Professional+ 且改非草稿文件要 Full 席位；桌面 server 要 Dev/Full 席位；只有 Figma MCP catalog 里的客户端能连（VS Code/Cursor/Claude Code 等）。 beta 期免费、将来转用量计费（官方帮助页直抓所见）。
Plans and seats are hard gates: the remote server is available on all plans but writing to the canvas needs Professional+ and editing non-draft files needs a Full seat; the desktop server needs a Dev/Full seat; only clients in the Figma MCP catalog can connect (VS Code/Cursor/Claude Code etc.). Free during beta, moving to usage-based billing later (seen in the directly fetched official help page).
适合什么任务Best for: 适合：设计系统驱动的编码流（agent 按真实组件/变量生成代码）、代码↔画布双向流。不适合：不在 MCP catalog 的客户端（要开发者候补名单）；要免费写画布的团队（套餐门槛）。
Fits: design-system-driven coding flows (the agent generates code from real components/variables), code↔canvas two-way flow. Not a fit: clients outside the MCP catalog (needs the developer waitlist); teams wanting free canvas writes (plan gates).
传输方式Transport: Streamable HTTP 双入口：远程 mcp.figma.com/mcp（推荐）+ 桌面本地 http://127.0.0.1:3845/mcp。核验：developers.figma.com 文档直抓（2026-10-21）；端点 405（存在，GET 不接受）。
Streamable HTTP, two entry points: remote mcp.figma.com/mcp (recommended) + desktop local http://127.0.0.1:3845/mcp. Verified: developers.figma.com docs fetched directly (2026-10-21); endpoint returns 405 (exists, GET not accepted).
认证机制Authentication: 首次连接走 Figma 账号登录（OAuth 语义）；无 token 明文配置路线的官方说明。席位类型（Dev/Full）决定能力面。
First connection goes through Figma account login (OAuth semantics); no official docs for a plaintext-token configuration route. The seat type (Dev/Full) determines the capability surface.
权限范围Permission scope: 读面：设计上下文、FigJam/Make、Code Connect；写面：画布 create/update（套餐+席位门槛）。客户端白名单（catalog）是 Figma 侧的接入闸门——这是它与多数 MCP server 最大的不同。
Read surface: design context, FigJam/Make, Code Connect; write surface: canvas create/update (plan + seat gates). The client whitelist (catalog) is Figma's side access gate — the biggest difference between it and most MCP servers.

头号误解Top misconception

把「beta 免费」当永久免费——官方明写将转 usage-based 付费Reading 'beta free' as free forever — the official docs state it will become usage-based paid
用 catalog 外的客户端硬连——官方只认 MCP catalog 名单Hard-wiring a client outside the catalog — Figma only accepts the MCP catalog list
把桌面 server 当推荐路线——官方 strong recommendation 是远程 server；桌面线是给企业/政府场景的Treating the desktop server as the recommended route — the official strong recommendation is the remote server; the desktop line serves enterprise/government needs
旧 help.figma.com 文章 URL 已 404——现役文档线在 developers.figma.com（2026-10-21 直抓）The old help.figma.com article URL 404s — the live docs line is developers.figma.com (direct-fetched 2026-10-21)

未知项清单Known unknowns

MCP catalog 完整客户端名单（未逐条清点）
usage-based 计费的定价细则（官方未给数字——报价记录约定不采价格）
远程与桌面形态的工具差异全表（未逐条对照）

The complete MCP catalog client list (not enumerated item by item)
Pricing details of usage-based billing (official gives no numbers — D9 discipline does not collect prices)
A full tool-difference table between the remote and desktop forms (not compared item by item)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-21。

类型Type	名称Name	链接Link
docs	Figma · 官方 MCP 开发者文档（双形态、端点、席位门槛，2026-10-21 直抓核验）Figma · official MCP developer docs (two forms, endpoints, seat gates, direct-fetched and verified 2026-10-21)	https://developers.figma.com/docs/figma-mcp-server/
docs	Figma · 官方帮助中心 MCP 入门（套餐与 beta 计费口径）Figma · official help-center MCP getting-started (plan and beta billing wording)	https://help.figma.com/hc/en-us/articles/39216419318551-Get-started-with-the-Figma-MCP-server
changelog	Figma · 官方 release notes（changelog）Figma · official release notes (changelog)	https://www.figma.com/release-notes/

实测记录Measured runs

本档未在真实客户端逐项跑通；工具清单与权限来自官方 README。

This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.