figmanage

io.github.dannykeanePublished by GitHub account dannykeanev1.5.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Lets an AI assistant manage a Figma workspace: find files, organize projects, review access, and handle teams, seats and offboarding.

What you can do
  • Find and browse files and recent work, and move files between projects
  • Review who has access to projects and files
  • Inspect teams and paid seats, including inactive-seat checks
  • Run offboarding handover checks and cleanup operations
  • Also usable as a command-line tool with JSON/JSONL output and dry-run checks
When to use it
Useful when you administer a Figma organization and want an assistant to answer questions about files, access, teams and seat usage, or to prepare offboarding and cleanup work. For design work itself, the README points to the official Figma MCP instead.
Requirements
Runs locally over stdio via npx, requiring Node.js 18+ and an MCP-capable client. Sign-in uses your Figma session in Chrome (may trigger a macOS Keychain prompt); some features such as comments and exports also need a Figma Personal Access Token added locally. Admin tasks require Figma admin access.
Before you install
It reads your Chrome session to sign in, so your Figma login is stored locally. Offboarding and cleanup operations can remove access, change file owners and downgrade seats; dry-run does not verify live permissions, so review the audit first. Keep tokens out of chat.

Installation

In SourceWeft

  1. Open figmanage in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

sh
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

sh
npm install -g figmanagefigmanage loginfigmanage 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:

sh
figmanage schemafigmanage 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

Source: README.md at commit 99ce621

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v1.5.2LatestOct 13, 2026
  2. v1.5.1Oct 8, 2026
  3. v1.5.0Sep 20, 2026
  4. v1.4.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts