Figmanage MCP Server

Manage your Figma workspace. 76 tools for files, projects, teams, permissions, and org admin.

Local serverstdio

What is the Figmanage MCP server?

Manage your Figma workspace. 76 tools for files, projects, teams, permissions, and org admin. Exposed over MCP by the figmanage mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Let agents manage your Figma workspace. Seats, teams, permissions, billing, offboarding, cleanup -- handled in conversation instead of clicking through admin panels.

Its toolset

Everything the assistant can do here goes through one of these:

  • list_favorites — Figma BigInt overflow bug on their server. favorite_file works fine
  • Variables — Enterprise-gated scopes
  • API — Auth
  • Internal — Session cookie
  • Public — Personal Access Token
  • Preset — What's included
  • starter — navigate, reading, comments, export
  • admin — navigate, org, permissions, analytics, teams, libraries
  • readonly — navigate, reading, comments, export, components, versions
  • full — everything (default)
  • check_auth — either
  • list_orgs — cookie

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at figmanage on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Figmanage's toolset — list_favorites, Variables, API and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dannykeane; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Figmanage's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Figmanage.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the figmanage mcp server does with a few real requests.

Available tools

ToolWhat it does
list_favoritesFigma BigInt overflow bug on their server. favorite_file works fine.
VariablesEnterprise-gated scopes.
APIAuth
InternalSession cookie
PublicPersonal Access Token
PresetWhat's included
starternavigate, reading, comments, export
adminnavigate, org, permissions, analytics, teams, libraries
readonlynavigate, reading, comments, export, components, versions
fulleverything (default)
check_autheither
list_orgscookie
switch_orgcookie
list_teamscookie

How to install the Figmanage MCP server

{
  "mcpServers": {
    "figmanage": {
      "command": "npx",
      "args": ["-y", "figmanage"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Figmanage to list favorites.
  • Use Figmanage to Variables.
  • Use Figmanage to API.

Frequently asked questions

It connects Figmanage to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (list_favorites, Variables, API, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Figmanage directly.