get_file_dataLABSCO SUMMARY
The Figma server to reach for when the file is too big for the others.
Chunking, a configurable memory limit and node-type filtering exist for one reason: design files that would otherwise exhaust the process or the context before you get an answer. On a small file this behaves like an ordinary Figma reader; on a large one it is the difference between an answer and a crash.
What it is
A Figma API server built for big files, with memory-aware processing, chunked retrieval and pagination on every listing call.
What you get
- File data retrieved in chunks, with page size, a memory ceiling in MB and a node-type filter set per call
- Resume for an interrupted retrieval, so a large file does not have to restart from zero
- Pagination on the listing operations (list_files)
- File metadata, components and styles (get_file_info, get_components, get_styles)
- Version history and comments on a file (get_file_versions, get_file_comments)
- Progress tracking and debug logging while a long retrieval runs
Requirements
A Figma access token, given either in the environment or in a JSON file you point the server at. Built from source with npm install and npm run build.
Setup effort
Build from source — git clone https://github.com/ArchimedesCrypto/figma-mcp-chunked.git
USE CASES
01
Reading a design file that is too large to load in one go
Retrieve it in pages with a memory ceiling, and resume if the run is interrupted.
02
Pulling the component inventory out of a design system
List the components and styles the file defines, rather than reading every node.
03
Finding out what changed and who said what
Read the version history alongside the comments left on the file.
04
Locating the right file in a Figma project
Page through the file list, then read the metadata of the one you want.
05
Extracting only the frames you care about
Filter retrieval to specific node types so components and frames come back without the rest of the document.
8 tools
Listed in project docs. Your client may show a different list.
list_filesget_file_versionsget_file_commentsget_file_infoget_componentsget_stylesget_file_nodesBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
FIGMA_ACCESS_TOKEN in your environment
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/ArchimedesCrypto/figma-mcp-chunked.git
cd figma-mcp-chunked
npm install
npm run buildTo use the build, add it to your client in that client's own format: node as the command, the full path to build/index.js in your clone as its argument, and FIGMA_ACCESS_TOKEN in the entry's env. The README gives no client entry for this route, only the start command node build/index.js --config=<YOUR_PATH_TO_CONFIG>.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"figma": {
"env": {
"FIGMA_ACCESS_TOKEN": "<YOUR_FIGMA_ACCESS_TOKEN>"
}
}
}
}
