Skip to main content
Glama

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.

Related MCP server: figma-pilot

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

Available Tools

4 tools
setup_extract_cookiesA

Read Figma sessions from Chrome for setup or recovery. Requires permission to read browser credentials; reuse permission already granted in this conversation. The user must be logged into Figma. macOS may show a Keychain prompt. Never returns cookies.

Inputs: no named parameters. Returns: error, result

setup_save_patA

Validate and save a PAT already supplied by the user. Prefer local figmanage login --pat-only to keep tokens out of chat. Rejects a PAT belonging to a different saved browser account.

Inputs: pat (required). Returns: error, result

setup_select_accountA

Validate and save a browser session after setup_extract_cookies. Use its recommended account without another question; ask when selection is ambiguous or changes the existing account. Preserves the PAT for the same account.

Inputs: account_index (required). Returns: error, result

setup_statusA
Read-only

Check live authentication, retry admin access detection, and get structured next actions. Use before setup, after an authentication error, or when expected tools are missing. Does not read browser credentials or change settings.

Inputs: no named parameters. Returns: error, result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    All four tools are setup-related but have distinct roles: status check, cookie extraction, account selection, and PAT saving. The only minor ambiguity is between setup_extract_cookies and setup_select_account, but their descriptions clearly separate extraction from validation/saving.

    Naming Consistency4/5

    All tools share a consistent setup_ prefix and use verb_noun naming (setup_status, setup_extract_cookies, setup_select_account, setup_save_pat). Minor deviation: setup_status is a noun phrase rather than verb_noun, but the pattern is otherwise uniform.

    Tool Count4/5

    Four tools is slightly thin for a setup workflow, but each tool covers a distinct step in the authentication/setup lifecycle. The count is appropriate for a focused setup-only server, though it may feel minimal if the server is expected to manage Figma resources beyond setup.

    Completeness4/5

    The setup flow is well covered: check status, extract cookies, select account, and save PAT. A minor gap is the lack of an explicit teardown/logout or re-authentication tool, but the status tool's 'next actions' guidance helps mitigate dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to create, modify, and manage Figma designs through natural language commands via a specialized MCP server and plugin bridge. It supports a wide range of operations including element creation, property modification, component management, and accessibility checks.
      4 npm
      105
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI clients to Figma, enabling real-time reading, creation, and modification of designs using natural language.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides write access to Figma through the Plugin API, enabling AI agents to create, modify, and manage Figma designs programmatically.
      23
      MIT