figmanage

Official registry Productivity

Let agents manage your Figma workspace. 102 tools for seats, teams, offboarding, and cleanup.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package figmanage
Claude Code
claude mcp add figmanage -- npx -y figmanage@1.5.2
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "figmanage": {
            "command": "npx",
            "args": [
                "-y",
                "figmanage@1.5.2"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. figmanage
  2. Try asking
  3. Get started with your agent
  4. Use the terminal
  5. For agents and scripts
  6. Already use the official Figma MCP?
  7. More help

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.

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

Frequently asked questions

What is figmanage?

Let agents manage your Figma workspace. 102 tools for seats, teams, offboarding, and cleanup.

How do I install figmanage?

It runs on your machine. In Claude Code: claude mcp add figmanage -- npx -y figmanage@1.5.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does figmanage need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is figmanage open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains figmanage?

It is published by dannykeane. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.