Figma

Figma

This connector works with Figma through the REST API (https://api.figma.com): team folders (formerly called projects), subfolders and their files, file metadata, pages, frames and layers, image exports, image fills, version history, comments and reactions, published components, component sets and styles, and Dev Mode resources. It authenticates with a personal access token, so it sees exactly the files the token's user can open. It does not edit designs: the REST API cannot change layers.

Setup (about 2 minutes)

1. In Figma open the account menu (top left in the file browser) → Settings → Security → Personal access tokens → Generate new token.
2. Name it (for example "AnythingMCP"), choose an expiry (at most 90 days; Figma no longer issues tokens that never expire) and set these scopes:
   • current_user:read, file_content:read, file_metadata:read, file_versions:read
   • file_comments:read and file_comments:write
   • library_content:read, library_assets:read, team_library_content:read
   • folders:read
   • file_dev_resources:read and file_dev_resources:write Tokens made before Figma renamed projects to folders may only carry projects:read; the folder tools need folders:read, so generate a new token if they answer 403 naming a scope.
3. Click Generate token, copy it right away (Figma shows it once) and paste it into FIGMA_ACCESS_TOKEN. When it expires, generate a new one and paste it again.

Read-only setup: leave out file_comments:write and file_dev_resources:write and switch off figma_post_comment, figma_delete_comment, figma_add_comment_reaction, figma_create_dev_resource and figma_update_dev_resource. figma_delete_dev_resource is installed switched off.

Finding things

• File key: the part after /design/ (or /file/, /board/, /slides/) in a file URL: https://www.figma.com/design/aBcD1234EfGh/Website → aBcD1234EfGh.
• Node ids: a link's node-id=12-345 is 12:345 in the API.
• Team id: the number after /team/ in the URL of a team page in the file browser. The API cannot list a user's teams, so ask the user for a team link. figma_list_team_folders → figma_list_subfolders (folders can be nested) → figma_list_folder_files then lead to file keys. A folder id is also the long number in a folder's URL in the file browser.
• Component and style keys (not node ids) come from the library list tools or from a file's components and styles maps.

Reading designs efficiently: start with figma_get_file_meta (cheap), then figma_get_file with depth 1 or 2 to see pages and top-level frames, then figma_get_file_nodes for the frames that matter. Whole documents are very large; answers over 200 KB are cut and marked _truncated. To see a screen, figma_render_images returns PNG, JPG, SVG or PDF URLs, valid for 30 days.

Rate limits: Figma limits per user and per plan of the file, in three tiers. File content, node reads and image renders (figma_get_file, figma_get_file_nodes, figma_render_images) are the tightest: on a paid plan with a Full or Dev seat 10 to 20 a minute, but for files on the free Starter plan, or for View and Collab seats, only a handful a month. Comments, versions, image fills, folders and dev resources allow 5 (Starter) to 100 a minute; metadata, components and styles 10 to 150. Over a limit Figma answers 429 with Retry-After; wait that long. Prefer metadata and single nodes over whole files.

Comments: figma_post_comment posts as the token's user; pin it with client_meta ({"node_id": "1:2", "node_offset": {"x": 0, "y": 0}}) or reply with comment_id (top-level comments only). figma_delete_comment only works on the user's own comments.

Dev resources are Dev Mode links (tickets, docs, code) on nodes; Dev Mode needs a paid plan and a Full or Dev seat. Without Dev Mode access to a file (a Starter or locked team, a View or Collab seat) Figma answers "File not found" to the dev resource tools, even for a file the other tools read fine: tell the user that Dev Mode is not available to them on that file rather than that the file is missing. At most 10 per node and each URL once per node; refused ones come back in errors, which this connector reports as a failed call.

Errors: 401 "Invalid token" means the token is wrong, expired or revoked: generate a new one. 403 means the token lacks the scope for the call (the message names the scopes) or the user has no access to that team or folder. 404 means no such file or node, or the user cannot open the file (for dev resources, see above). 400 names an invalid parameter, e.g. a node id with a hyphen instead of a colon. 429 is a rate limit (see above). Library endpoints refuse a branch key: use the main file's key.

Out of scope here: editing designs, variables (Enterprise only), webhooks, FigJam and Slides content beyond the file tree, and library analytics.