Connect Figma to Claude Code
Read design files, nodes, components, styles and comments, and render images. Add Toolspoke to Claude Code once and it can use 12 Figma actions. Your Figma credential stays in Toolspoke, and you choose which actions Claude Code may call.
Set it up in Claude Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcpThe sign-in opens in your browser, and Toolspoke asks you to approve it.
Install Figma and connect it
Add Figma to a project in your Toolspoke workspace.
Personal access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- Personal access token
- Figma → Settings → Security → Personal access tokens. Grant file_content:read, file_comments:read, file_versions:read, projects:read and current_user:read, plus file_comments:write only if this install should post comments.
Choose what Claude Code may do
All 12 actions start on. Switch off the one action that changes something in Figma, and Claude Code gets a refusal if it tries.
What you can ask Claude Code for
A few of the Figma actions that only read, so they are safe to try first.
- Return the Figma user the token belongs to: id, handle, email and avatar
- List the projects inside one Figma team, with their ids and names
- List the files in one project, each with the file key, name and last-modified time
- Fetch a file's document tree: pages, frames, and every layer with its geometry, styles and text
What Claude Code can do in Figma
11 actions read and one writes.
Reads
Get me
Return the Figma user the token belongs to: id, handle, email and avatar. Call it to confirm which account a connection is acting as. It is the cheapest call here and takes no arguments, which is why it is the connection's health check.
List team projects
List the projects inside one Figma team, with their ids and names. This is the top of the discovery chain: team id, then list_project_files for the file keys, then the file operations. The team id is the number in a Figma team URL, figma.com/files/team/1234567890/….
List project files
List the files in one project, each with the file key, name and last-modified time. The file key it returns is what every other operation here takes, a file key is not the same as the numeric project id, and it cannot be guessed from a file name. Get the project id from list_team_projects.
Get file
Fetch a file's document tree: pages, frames, and every layer with its geometry, styles and text. Start with depth 2, that returns the pages and their top-level frames with node ids and nothing else, which is usually all you need to find the frame you actually care about. A full-depth call on a real design file is enormous and will exhaust your context; once you have the node id, call get_file_nodes for that subtree instead.
Get file nodes
Fetch specific nodes from a file as structured JSON, one frame, one component, one screen, with their children, layout constraints, auto-layout padding and spacing, fills, strokes, effects and text styles. This is the operation to reach for when implementing a design: it gives an agent the actual measurements and tokens instead of a picture it has to guess from. Get node ids from get_file at a shallow depth, or from the node-id parameter of a Figma URL (convert the URL's 1-42 form to 1:42). Pair it with get_image_renders when you also want to see the frame.
Get image renders
Render nodes to images and return short-lived URLs, keyed by node id. Use it to actually look at a frame, png or jpg for a screenshot, svg for an icon you intend to copy into code, pdf for a print asset. The URLs expire after about 30 days, so treat them as something to fetch now rather than store. This shows what a design looks like; get_file_nodes tells you what it measures, and an implementation usually needs both.
Get file components
List the components published from a file, with their key, node id, name, description and containing frame. This is the design system as the file declares it: call it before building any UI from a file so an implementation reuses the components a team already named. Button/Primary, Card/Elevated, instead of inventing parallel ones. Feed a component's node id to get_file_nodes for its structure, or to get_image_renders to see it. The file key must be the main file, not a branch: publishing does not happen from branches.
Get file component sets
List the component sets published from a file, the variant groups, such as one Button set holding every size and state. Use it after get_file_components when a component name looks like it has variants: the set is what tells you which properties (size, state, icon) the component actually accepts. Main file key only, not a branch.
Get file styles
List the styles published from a file, colour, text, effect and grid styles, with their key, node id, name and description. These are the design tokens by the names the team uses. Read them before writing any CSS from a Figma design so the implementation refers to Brand/Primary rather than a hex code copied out of a node. Main file key only, not a branch.
Get comments
List the comments on a file, with their author, timestamp, resolution state and the node or coordinate they are pinned to. Use it to find out what reviewers asked for on a specific frame before implementing it, and to get the comment id that post_comment needs in order to reply in the same thread rather than starting a new one.
Get file versions
List a file's version history, newest first, with each version's id, label, description and author. Use it to see what changed and when, and to take a version id you can then pass to get_file, get_file_nodes or get_image_renders to read the design as it stood at that point rather than as it is now.
Writes
Post comment
Post a comment on a file. Everyone with access to the file sees it and Figma notifies the people watching, so write it as a message to designers, not as a note to yourself. Pass reply_to_comment_id with a comment id from get_comments to reply inside an existing thread; omit it to start a new one at the top level of the file.
Figma in Claude Code: questions
Does Claude Code see my Figma credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Can I stop Claude Code from changing things in Figma?
Yes. Each of the 12 actions can be switched off for a project. Turn off the one that changes something and Claude Code can only read.
Will 12 actions crowd Claude Code's context?
No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Figma action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Can I add it once for every project?
Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.
What does it cost?
Tool calls are free on every plan, and a Figma call does not run in a sandbox, so it bills nothing.
Figma in your other apps
More design toolkits for Claude Code
Try Figma in Claude Code
Free to start, and tool calls cost nothing on any plan.