get-file-infoLABSCO SUMMARY
Design decisions become answerable outside Figma.
It turns a file into things you can query — which components exist, what the styles are, what the screens actually say — so handoff questions get answered from the file itself rather than from a screenshot or a second-hand description.
What it is
A read layer over Figma's API. It runs locally against your Figma files and returns the parts of a design that people outside the tool normally have to ask for: the component inventory, the style definitions, the text on the screens, and the comments left on them.
What you get
- A file's information and structure, or just the nodes you name
- Every component a file defines, and the styles beside them
- All of the text extracted from a design, so UI copy can be read as copy
- Search within a file, for when you know the element exists but not where
- The comments left on a file
Requirements
Node.js 16 or higher and a Figma personal access token, which you create in your Figma account settings and pass to the server as an environment variable. The repository is cloned and built locally — npm install, npm run build — rather than installed from a registry.
Setup effort
Build from source — git clone https://github.com/mohammeduvaiz/figma-mcp-server.git
USE CASES
01
Reviewing the copy in a design
Pull every string out of the screens and read them together, so tone, terminology and length problems surface before anything is built.
02
Writing the handoff notes for a screen
Name the nodes you care about and read back their structure and the styles applied to them, instead of measuring off an image.
03
Auditing a design system
List the components a file defines with the styles beside them, to find where the same thing has been built twice.
04
Catching up on feedback
Read the comments left on a file together with the part of the design each one points at.
05
Finding something in a large file
Search by name when you know the element is in there but not which page it lives on.
7 tools
Listed in project docs. Your client may show a different list.
get-nodesget-componentsget-stylesget-commentssearch-fileextract-textBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation. All seven only read; nothing creates a frame, edits a layer or posts a comment. analyze-design-system, extract-ui-copy and generate-dev-handoff are prompts, not tools.
Requires
- Node.js 16 or later
- FIGMA_API_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/mohammeduvaiz/figma-mcp-server.git
cd figma-mcp-server
npm installCreate a .env file in the project root with FIGMA_API_TOKEN, API_KEY, TRANSPORT_TYPE
TERMINAL
npm run build
npm startMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"figma": {
"command": "node",
"args": [
"<YOUR_PATH_TO_FIGMA_MCP_SERVER>/build/index.js"
],
"env": {
"FIGMA_API_TOKEN": "<YOUR_FIGMA_API_TOKEN>",
"TRANSPORT_TYPE": "stdio"
}
}
}
}<YOUR_PATH_TO_FIGMA_MCP_SERVER> is the full path of your clone, and <YOUR_FIGMA_API_TOKEN> is your Figma personal access token (from your Figma account settings).
