| name | figma-install-auth |
| description | Set up Figma REST API authentication with personal access tokens or OAuth 2.0.
Use when connecting to the Figma API, generating tokens, configuring scopes,
or setting up OAuth flows for Figma integrations.
Trigger with phrases like "install figma", "setup figma API",
"figma auth", "figma personal access token", "figma OAuth".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(curl:*), Grep |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","figma"] |
| compatibility | Designed for Claude Code |
Figma Install & Auth
Overview
Configure authentication for the Figma REST API. Figma supports two auth methods: Personal Access Tokens (PATs) for scripts and server-side tools, and OAuth 2.0 for apps that act on behalf of users. All requests go to https://api.figma.com.
Prerequisites
- Figma account (Free, Professional, or Enterprise)
- Node.js 18+ (for JS/TS integrations)
- A Figma file key (the string after
/design/ in a Figma URL)
Instructions
Step 1: Generate a Personal Access Token
- Open Figma > Settings > Account > Personal access tokens
- Click Generate new token
- Name the token and assign scopes:
| Scope | Access | Use Case |
|---|
file_content:read | Read file JSON | Inspecting layers, extracting design tokens |
file_content:write | Modify files | Programmatic design updates |
file_comments:read | Read comments | Review tooling |
file_comments:write | Post comments | Automated feedback |
file_dev_resources:read | Dev resources | Dev mode integrations |
file_variables:read | Read variables | Design token sync |
file_variables:write | Write variables | Token pipeline |
webhooks:write | Manage webhooks | Event-driven automation |
- Copy the token immediately -- it is shown only once
- PATs expire after a maximum of 90 days
Step 2: Store Credentials Securely
FIGMA_PAT="figd_your-personal-access-token"
FIGMA_FILE_KEY="abc123XYZdefaultFileKey"
.env
.env.local
.env.*.