Figma MCP server with chunking and pagination
Connect Figma MCP Chunked to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Figma MCP server with chunking and pagination. The figma mcp chunked mcp server is what makes that connection.
A Model Context Protocol (MCP) server for interacting with the Figma API, featuring memory-efficient chunking and pagination capabilities for handling large Figma files.
This MCP server provides a robust interface to the Figma API with built-in memory management features. It's designed to handle large Figma files efficiently by breaking down operations into manageable chunks and implementing pagination where necessary.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_files — The list_files tool exposed by this serverget_file_versions — The get_file_versions tool exposed by this serverget_file_comments — The get_file_comments tool exposed by this serverget_file_info — The get_file_info tool exposed by this serverget_components — The get_components tool exposed by this serverget_styles — The get_styles tool exposed by this serverget_file_nodes — The get_file_nodes tool exposed by this serverConfiguration is passed through the environment: FIGMA_ACCESS_TOKEN, DEBUG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Figma MCP Chunked's toolset — list_files, get_file_versions, get_file_comments and 4 more — is a fair guide to whether it matches your workflow. It is maintained by ArchimedesCrypto; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_files | The list_files tool exposed by this server. |
| get_file_versions | The get_file_versions tool exposed by this server. |
| get_file_comments | The get_file_comments tool exposed by this server. |
| get_file_info | The get_file_info tool exposed by this server. |
| get_components | The get_components tool exposed by this server. |
| get_styles | The get_styles tool exposed by this server. |
| get_file_nodes | The get_file_nodes tool exposed by this server. |
{
"mcpServers": {
"figma": {
"env": {
"FIGMA_ACCESS_TOKEN": "your-access-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| FIGMA_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| DEBUG | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.