Back to Browse

Figmanage MCP Server

DesignUse Caution3.8Local
Free

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

About

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

Security Report

3.8
Use Caution3.8High Risk

Figmanage is a Figma workspace management MCP server whose permissions match its stated purpose, and its code shows deliberate guardrails such as audit-by-default and confirm flags on destructive actions. The main concerns are the breadth of destructive admin operations (offboarding, seat changes, permission and team deletion) exposed to an AI agent, and the reliance on a browser session cookie, which carries the user's full privileges. The visible code shows no exfiltration or malicious patterns, but the truncated compound-manager file prevents a full review of the offboarding write path. Supply chain analysis found 7 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

4 files analyzed · 12 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

env_vars

Check that this permission is expected for this type of plugin.

database

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

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

Getting Started

Once installed, try these example prompts and explore these capabilities:

  • 1"Which paid seats haven't been active in 30 days? How much would we save?"
  • 2"Offboard sarah@company.com -- show me everything she owns, then transfer it to jake and remove her from the org"
  • 3"Set up a new hire: invite alex@company.com to Design and Engineering as an editor"
  • 4"Create a user group called Platform Design and add the three designers"
  • 5"Run a quarterly design ops report for the org"
  • 6"Audit permissions on the Platform team -- flag any external users or overshared files"
  • 7"Show me our billing history and current seat breakdown"
  • 8"Clean up the Mobile App project -- find stale files and archive dead branches"
  • 9"What are the unresolved comments across the Platform project?"
  • 10"Export all the icons from the Design System file as SVGs"
  • 11"Move the Q4 files into the Archive project"
  • 12"Share the Homepage mockup with alex@company.com and set link access to view-only"
  • 13"Summarize the Brand Guidelines file -- pages, components, styles"

Documentation

View on GitHub

From the project's GitHub 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

Reviews

No reviews yet

Be the first to review this server!

Version History

v1.3.5Mar 21, 2026Re-scanned
v1.3.3Mar 20, 2026Re-scanned
v1.3.2Mar 20, 2026Re-scanned