mcpField
F
figmanage

figmanage

Local
github.com/dannykeaneProductivity8Updated 2w ago
Repository

About figmanage

figmanage is an MCP server and CLI for managing Figma workspaces, aimed at teams and administrative workflows. It covers file organization, access reviews, teams, and seats, using the permissions of the signed-in Figma account.

Key features

  1. 01Find and organize files
  2. 02Review project access
  3. 03Manage teams and seats
  4. 04Support offboarding workflows
  5. 05MCP and CLI operation

Use cases

  1. 01Find recently edited files
  2. 02Move files into an archive project
  3. 03Review who can access a project
  4. 04Handle a departing team member

MCP support

figmanage runs as a local MCP server and gives compatible agents tools for managing Figma workspaces.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "dannykeane-figmanage": {
      "command": "npx",
      "args": [
        "-y",
        "figmanage"
      ]
    }
  }
}
Run commandnpx -y figmanage

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmfigmanage1.5.2

Tools

4

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project README

figmanage

Manage your Figma workspace with your agent or terminal.

Find files, organize projects, review access, and manage teams and seats. Connect Figmanage to your AI assistant through MCP, or use the command-line tool yourself.

npm CI

Try asking

  • “Find the files I worked on this week.”
  • “Move these files into the Archive project.”
  • “Show who has access to this project.”
  • “Which paid seats have been inactive for 30 days?”
  • “Check what needs handing over before Jordan leaves.”

Figmanage uses your Figma permissions. Admin tasks need admin access.

Get started with your agent

You need Node.js 18+ and an agent that supports local MCP servers.

1. Add Figmanage. In Claude Code, run:

claude mcp add --transport stdio --scope user figmanage -- npx -y figmanage --mcp

Using Codex, Cursor, VS Code, or Claude Desktop? Generate your client config.

2. Sign in to Figma in Chrome, then ask your agent:

Set up Figmanage, then show my teams and recent files.

Your agent asks before reading your Chrome session. macOS may show a Keychain prompt. Your login is saved locally.

3. Give it a task. Start with one of the examples above.

Some features, such as comments and exports, also need a Figma Personal Access Token. Add it locally with npx -y figmanage login --pat-only, then reconnect MCP. Keep tokens out of chat. See account setup.

Use the terminal

npm install -g figmanage
figmanage login
figmanage navigate list-recent-files

Use figmanage --help to find commands, or figmanage doctor if setup needs attention.

For agents and scripts

Use MCP for tool discovery, or the CLI for automation:

figmanage schema
figmanage navigate list-recent-files --jsonl --no-input
  • Readable by humans: terminal output stays easy to scan.
  • Readable by scripts: choose --json or --jsonl. With JSONL, require the final summary and check the exit code.
  • Check before changing: --dry-run checks inputs without sending requests. It does not check live permissions.
  • Follow progress: offboarding supports --progress --jsonl and MCP progress notifications when requested.

See the automation guide for output formats and the optional agent skill for workflow recipes.

Already use the official Figma MCP?

Use Figmanage to manage files, access, teams, and seats. Use the official Figma MCP for design work. Your agent can pass file links between them; each server has its own login. How they work together.

More help

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.