How do I install Figmanage?

Figmanage is a local plugin. Install it using npm package: figmanage and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Figmanage safe to use?

Yes. Figmanage passed MCP Marketplace's automated security scan with a score of 9/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Figmanage need?

Figmanage requires the following credentials or environment variables: FIGMA_PAT, FIGMA_AUTH_COOKIE. You can find setup instructions on the server detail page.

What AI apps work with Figmanage?

Figmanage uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Figmanage MCP Server

by dannykeane

DesignLow Risk9.0Local

Free

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

About

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

Every Figma MCP is design-to-code. figmanage is the management layer: 102 tools that let agents operate on the workspace itself. Works with Claude Code, Cursor, OpenClaw, or as a standalone CLI.

Built for design leads, designers, and design/org managers who manage Figma workspaces -- and want access from the terminal or through agents.

Two API surfaces under the hood. A Personal Access Token covers reading, comments, export, components, versions, webhooks, and variables.

The session cookie unlocks the internal API -- org admin, billing, seats, permissions, analytics, search, and compound operations that chain multiple calls together.

Auto-detects admin status at startup -- non-admins see 68 tools, admins see all 102.

No env vars or config files needed. On first run, figmanage walks you through setup right in the conversation -- extracts your Chrome session cookie, asks you to create a PAT, and stores credentials locally. Just add the server and start talking.

Security Report

9.0

Low Risk9.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). 2 known CVEs in dependencies Package registry verified. Imported from the Official MCP Registry.

4 files analyzed · 3 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.

env_vars

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

file_system

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

What You'll Need

Set these up before or after installing:

Figma Personal Access TokenRequired

Environment variable: FIGMA_PAT

Session cookie (unlocks tool usage) - just login to Figma.Required

Environment variable: FIGMA_AUTH_COOKIE

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"