figmanage

Figma workspace management from the command line. 85 commands for seats, teams, permissions, billing, onboarding, and org admin. Also works as an MCP server for AI assistants.

install

npm install -g figmanage

setup

figmanage login

Extracts your Chrome session cookie, prompts for a PAT, and stores credentials locally at ~/.config/figmanage/. One-time setup -- no env vars, no JSON config editing.

figmanage whoami    # verify auth
figmanage logout    # clear credentials

usage

figmanage seat-optimization                      # find inactive paid seats
figmanage offboard sarah@co.com                  # audit what a user owns
figmanage offboard sarah@co.com --execute \
  --transfer-to jake@co.com                      # execute the offboarding
figmanage onboard alex@co.com --teams 123,456 \
  --role editor --seat full --confirm            # set up a new hire
figmanage quarterly-report                       # org-wide design ops snapshot
figmanage members --search danny                 # find org members
figmanage teams                                  # list all teams
figmanage permissions file abc123                # who has access to a file
figmanage permission-audit --scope team --id 789 # audit a team's permissions
figmanage branch-cleanup 573408414               # find stale branches

All commands output JSON when piped or when --json is passed.

AI integration (MCP)

figmanage runs as an MCP server for Claude, ChatGPT, Cursor, and other AI assistants:

# Claude Code
claude mcp add figmanage -- npx -y figmanage --mcp

# Claude Desktop / Cowork
# Add to claude_desktop_config.json:
{
  "mcpServers": {
    "figmanage": {
      "command": "npx",
      "args": ["-y", "figmanage", "--mcp"]
    }
  }
}

Credentials are read from ~/.config/figmanage/ (set up via figmanage login). Env vars (FIGMA_PAT, FIGMA_AUTH_COOKIE, etc.) override the config file for backwards compatibility.

MCP mode exposes all 85 tools to the AI assistant. HTTP transport available via --mcp --http <port>.

toolset presets (MCP only)

Use FIGMA_TOOLSETS to expose only specific tool groups:

auth

figmanage uses two Figma API surfaces:

Cookie auth unlocks all 85 tools. PAT-only gives ~30 (reading, comments, export, components). Both together is recommended.

Auth resolution: env vars > config file > prompt to run figmanage login.

commands

navigate (10)

files (8)

projects (6)

permissions (7)

reading (2)

components (4)

versions (2)

branching (3)

comments (4)

export (2)

webhooks (4)

variables (3, Enterprise)

analytics (2)

org (12)

teams (3)

libraries (1)

compound (12)

Multi-step operations that aggregate data from several API calls.

security

All parameters that accept Figma IDs are validated against /^[\w.:-]+$/ before use. Rate limit retries are restricted to safe HTTP methods. Mutations are never retried. Billing responses strip PII. Destructive operations default to dry-run mode. Config file is stored with 0o600 permissions.

known limitations

• list_favorites: Figma BigInt overflow bug on their server. favorite_file works fine.
• Branch merging: Requires Figma's multiplayer protocol, no REST endpoint.
• Cookie expiry: ~30 days. Run figmanage login --refresh to renew.
• Windows cookies: Best-effort DPAPI extraction. Falls back to PAT-only.
• Variables: Enterprise-gated scopes.
• get_file: Returns full document tree. Use depth param or get_nodes.

development

git clone https://github.com/dannykeane/figmanage.git
cd figmanage
npm install
npm run build
npm test

license

MIT