Thin typed wrapper around the Figma REST API
Thin typed wrapper around the Figma REST API. Exposed over MCP by the figma mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
JavaScript client-side implementation of the Figma REST API.
Everything the assistant can do here goes through one of these:
Authentication — Creates new Api object with specified personalAccessToken or oAuthToken. For details about how to get these tokens, [see theEndpoints — All these endpoints methods receive objects like pathParams, queryParams, requestBody, as arguments, and return a Promise. For details about theFiles — The Files tool exposed by this serverComments — The Comments tool exposed by this serverUsers — The Users tool exposed by this serverProjects — The Projects tool exposed by this serverWebhooks — The Webhooks tool exposed by this serverPayments — The Payments tool exposed by this serverVariables — The Variables tool exposed by this serverAnalytics — The Analytics tool exposed by this serverfigma-api on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
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's toolset — Authentication, Endpoints, Files and 7 more — is a fair guide to whether it matches your workflow. It is maintained by didoo; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Authentication | Creates new Api object with specified personalAccessToken or oAuthToken. For details about how to get these tokens, [see the documentation](https://www.figma.com/developers/api#authentication) |
| Endpoints | All these endpoints methods receive objects like pathParams, queryParams, requestBody, as arguments, and return a Promise. For details about the shape of these objects refer to the official Figma REST API documentation ( |
| Files | The Files tool exposed by this server. |
| Comments | The Comments tool exposed by this server. |
| Users | The Users tool exposed by this server. |
| Projects | The Projects tool exposed by this server. |
| Webhooks | The Webhooks tool exposed by this server. |
| Payments | The Payments tool exposed by this server. |
| Variables | The Variables tool exposed by this server. |
| Analytics | The Analytics tool exposed by this server. |
{
"mcpServers": {
"figma-api-server": {
"command": "npx",
"args": ["-y", "figma-api"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
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.