跳过安装。2 分钟内即可运行。
在 cloud.anythingmcp.com 开始免费试用，一键添加 Figma，然后将你的 AI 客户端（Claude、ChatGPT、Copilot 或 Cursor）指向生成的 MCP 端点。无需 Docker，无需 git clone，无需任何工程经验。
摘要
让你的 AI 读取你的 Figma 设计：浏览团队文件夹和文件，查看页面、画框和图层，导出图片，查找组件和样式，追踪版本历史，阅读和发布评论，并管理 Dev Mode 链接。使用个人访问令牌。
试试这样问
Figma 的示例提示
点击任意提示即可复制，然后粘贴到 Claude、ChatGPT、Cursor、Gemini、Copilot 或 OpenClaw 中，在该连接器上运行。
Claude 是 AI，可能会出错。请核对回答。
💡 无需安装? 直接使用 cloud.anythingmcp.com。 登录、点击 Connectors → Figma、粘贴凭证、生成 MCP API key，即可完成。无 Docker、无
git clone、无本地服务器。
Figma
让你的 AI 读取你的 Figma 设计：浏览团队文件夹和文件，查看页面、画框和图层，导出图片，查找组件和样式，追踪版本历史，阅读和发布评论，并管理 Dev Mode 链接。使用个人访问令牌。
设置
- 在 Figma 中打开账户菜单（文件浏览器左上角）→ Settings → Security → Personal access tokens → Generate new token。
- 为令牌命名（例如 "AnythingMCP"）并选择有效期：最长 90 天，Figma 已不再签发永不过期的令牌。勾选以下权限范围：
current_user:read,file_content:read,file_metadata:read,file_versions:readfile_comments:read,file_comments:writelibrary_content:read,library_assets:read,team_library_content:readfolders:readfile_dev_resources:read,file_dev_resources:write
- 点击 Generate token 并立即复制：Figma 只显示一次。令牌通常以
figd_开头。 - 把令牌填入
FIGMA_ACCESS_TOKEN，不要带 Bearer 字样，然后安装连接器。 - 先运行
figma_get_me：它会显示该令牌属于哪个 Figma 用户。然后把文件链接发给 AI：文件 key 就是 URL 中/design/后面的部分。
令牌有效期：令牌最长有效 90 天。过期后，用相同的权限范围生成新令牌，再次填入 FIGMA_ACCESS_TOKEN。连接器能看到的正是令牌所属用户可以打开的文件和团队。在 Figma 把项目改名为文件夹（folders）之前创建的令牌可能只有 projects:read，而文件夹相关工具需要 folders:read：如果它们返回 403 并指出某个权限范围，请生成新令牌。
查找团队和文件夹：Figma 的 API 无法列出你所在的团队。请把文件浏览器中某个团队页面的链接发给 AI（团队 id 是 /team/ 后面的数字）；之后通过 figma_list_team_folders, figma_list_subfolders 和 figma_list_folder_files 就能找到文件。
权限和只读设置：不要授予 file_comments:write 和 file_dev_resources:write，并关闭 figma_post_comment, figma_delete_comment, figma_add_comment_reaction, figma_create_dev_resource 和 figma_update_dev_resource。AI 发布的评论会以令牌所属用户的名义显示，所有能访问该文件的人都能看到。
安装时默认关闭：figma_delete_dev_resource，它会为所有人从节点上删除一个 Dev Mode 链接。只有在 AI 需要删除 dev resource 时才打开它。
速率限制和 Starter 方案：Figma 按用户以及文件所属的方案限制请求。读取文件内容、节点和渲染图片（figma_get_file, figma_get_file_nodes, figma_render_images）的限制最严：在拥有 Full 或 Dev 席位的付费方案中每分钟 10 到 20 次，但对于免费 Starter 方案中的文件，或使用 View、Collab 席位时，每月只有寥寥几次。元数据、评论、版本、组件和样式的额度要宽松得多。请让 AI 查看单个画框，而不是整个文件；非常大的响应会在 200 KB 处截断。渲染图片的链接有效期为 30 天。
Dev Mode：dev resource（附加在节点上的工单、文档或代码链接）需要付费方案以及 Full 或 Dev 席位。没有 Dev Mode 访问权限时，即使其他工具能正常读取该文件，Figma 也会对 dev resource 工具返回 "File not found"。每个节点最多 10 个 dev resource，同一 URL 只能添加一次。
常见错误：401 "Invalid token" 表示令牌错误、已过期或已被撤销：请生成新令牌。403 表示令牌缺少某个权限范围（消息中会指出），或该用户无权访问那个团队或文件夹。404 表示文件或节点不存在，或该用户无法打开该文件：请从文件 URL 中重新复制 key。400 会指出无效参数，例如节点 id 用了连字符而不是冒号（链接中的 node-id=12-345 对应 12:345）。429 表示触发了速率限制：稍等后再试。库相关工具不接受分支（branch）的 key：请使用主文件的 key。
连接器不会编辑设计，也不处理变量、Webhook、文件树之外的 FigJam 和 Slides 内容，以及库分析。
前提条件: FIGMA_ACCESS_TOKEN
本地安装连接器
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
打开 http://localhost:3000/connectors/store，选择 Figma 并填入前提条件中列出的环境变量。
可用工具
| Tool | What it does |
|---|---|
figma_get_me | Get the Figma user the token belongs to: id, handle, email and avatar URL |
figma_get_file_meta | Get a file's metadata without its content: name, folder name, editor type (figma, figjam, slides ...), creator, last_touched_at and by… |
figma_get_file | Read a file's document tree: pages, frames and layers with their ids, names, types, sizes, fills, text and layout, plus the components and… |
figma_get_file_nodes | Read specific nodes (frames, components, layers) of a file with everything below them: type, name, absolute bounding box, fills, strokes… |
figma_render_images | Render nodes of a file as PNG, JPG, SVG or PDF and get a download URL per node id (null when a node could not be rendered) |
figma_get_image_fills | Get download URLs for every image used as a fill in a file, keyed by imageRef (the imageRef in a node's fills) |
figma_list_versions | List a file's version history, newest first: id, label and description of named versions, created_at, the user and thumbnail |
figma_list_comments | List all comments on a file: id, message, user, created_at, resolved_at, parent_id (for replies), client_meta (where it is pinned: node_id… |
figma_post_comment | Post a comment on a file as the token's user, optionally pinned to a node or a point, or as a reply to a top-level comment (comment_id) |
figma_delete_comment | Delete a comment |
figma_list_comment_reactions | List the emoji reactions on a comment: emoji, user and created_at |
figma_add_comment_reaction | React to a comment with an emoji shortcode, as the token's user; it shows next to the comment |
figma_list_team_folders | List the top-level folders (formerly called projects) of a team that the token's user can see: id, name, parent_folder_id (null at the… |
figma_list_subfolders | List the folders directly inside a folder (folders can be nested): id, name, parent_folder_id and created_at, plus the parent folder's name |
figma_list_folder_files | List the files directly in a folder (not in its subfolders): key, name, thumbnail_url and last_modified, plus the folder's name |
figma_list_team_components | List the published components of a team library: key, name, description, the file and node they live in, thumbnail and who last updated them |
figma_list_team_component_sets | List the published component sets (components with variants) of a team library: key, name, description, the file and node they live in… |
figma_list_team_styles | List the published styles (colors, text, effects, grids) of a team library: key, name, description, the file and node they live in… |
figma_list_file_components | List the published components of a library file: key, name, description, node_id and thumbnail |
figma_list_file_component_sets | List the published component sets of a library file: key, name, description, node_id and thumbnail |
figma_list_file_styles | List the published styles of a library file: key, name, description, node_id and thumbnail |
figma_get_component | Get one published component by its key: name, description, the file and node it lives in, its containing frame and component set, thumbnail… |
figma_get_component_set | Get one published component set (a component with variants) by its key: name, description, file, node and thumbnail |
figma_get_style | Get one published style by its key: name, description, style_type (FILL, TEXT, EFFECT, GRID), the file and node it lives in and thumbnail |
figma_list_dev_resources | List the dev resources of a file: links that developers attached to nodes in Dev Mode (tickets, docs, code), each with id, name, url and… |
figma_create_dev_resource | Attach a link (a ticket, a doc, a code file) to a node as a dev resource, visible to everyone in Dev Mode |
figma_update_dev_resource | Change the name or URL of a dev resource |
figma_delete_dev_resource | Remove a dev resource link from a node, for everyone |
示例提示
- “列出 Checkout redesign 文件的页面和主要画框，以及最后编辑它的人。”
- “Checkout redesign 文件中哪些评论还没有解决？分别是谁写的？”
- “把 Acme 官网文件中的价格页画框导出为 PNG，并给我链接。”
- “回复 Lena 在 Checkout redesign 文件中的评论，告诉她按钮颜色已经更新。”
下一步
这份指南对你有帮助吗?
