get-fileLABSCO SUMMARY
Read access to Figma files is the working surface.
Reading files and listing them is what the author reports as tested and functional. Variable and theme management is written into the server but not enabled — Figma's API does not expose it — so plan around reading designs, not writing design tokens.
What it is
A read path into Figma's API: the files available to your token, and one file's contents. Both stdio and SSE transports are supported.
What you get
- The Figma files your token can reach
- One file's contents, read through the API
- Responses cached, rate limits handled, and usage statistics tracked
Requirements
Node.js 18.x or newer and a Figma access token in the environment as FIGMA_ACCESS_TOKEN. Build the server, then point your client at dist/index.js using an absolute path — a relative one does not resolve.
Setup effort
Build from source
USE CASES
01
Finding the right file in a project
The file list comes into the conversation, so the search does not start with opening Figma in a tab.
02
Answering a question about a design without opening Figma
The file's contents are readable in place, which is enough for the questions that only need to know what is there.
03
Bringing a design into a coding session
List, then read, so the implementation is written against the file rather than against a screenshot of it.
4 tools
Listed in project docs. Your client may show a different list.
list-filescreate-variablescreate-themeBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation. Only get-file and list-files work; create-variables and create-theme need write access that Figma's REST API does not give personal access tokens.
Requires
- Node.js 18 or later
- FIGMA_ACCESS_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/TimHolden/figma-mcp-server
cd figma-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"figma": {
"command": "node",
"args": [
"<YOUR_PATH_TO_FIGMA_MCP_SERVER>/dist/index.js"
],
"env": {
"FIGMA_ACCESS_TOKEN": "<YOUR_FIGMA_ACCESS_TOKEN>"
}
}
}
}<YOUR_PATH_TO_FIGMA_MCP_SERVER> is the full path of your clone — npm run build creates dist/index.js there. A relative path does not work, and on Windows use double backslashes.
