What can you do with this server?

The server currently provides only setup operations to authenticate figmanage. After setup, additional tools would be available, but the schema exposed here only supports the following: * setup_status: Check figmanage authentication status and get setup instructions. * setup_extract_cookies: Extract Figma session cookies from Chrome (triggers a Keychain prompt on macOS). * setup_select_account: Select a Figma account from the extracted list and validate the session. * setup_save_pat: Validate and save a Figma Personal Access Token, completing setup and activating all tools.

Which integrations are available for this server?

Provides tools for managing a Figma workspace, including seats, teams, permissions, billing, offboarding, cleanup, file/project management, comments, exports, and user groups.

How do I use figmanage?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@figmanage find inactive paid seats and estimate potential savings" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ko ru zh

figmanage

by dannykeane

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

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

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

Setup and troubleshooting
Commands and all 102 operations
Offboarding and its limits — review the audit first. Execution can remove access, change file owners, and downgrade seats.
Contribute · Changelog · MIT license

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.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No
`result`	No

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes beyond the annotations by disclosing important behavioral traits: it requires permission to read browser credentials, may trigger a macOS Keychain prompt, and explicitly states it 'Never returns cookies' — a critical clarification given the tool name. This adds value beyond the sparse annotations and sets clear expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, each with a distinct purpose: state the action, list prerequisites, and disclose behavioral outcomes (keychain prompt, no cookies). It is front-loaded with the core purpose and avoids filler. Every sentence adds necessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with an output schema, the description covers all necessary context: prerequisites, permission requirements, potential system prompts, and what the tool does NOT return. The existence of an output schema handles return value details. The description is complete for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4. The description adds no parameter-specific details because none are needed. It does provide context about the operation's inputs (Chrome, Figma session) which is relevant but not parameter semantics. Since the schema is empty, no further clarification is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Read Figma sessions from Chrome for setup or recovery.' It identifies the specific verb (read) and resource (Figma sessions from Chrome), and the context (setup or recovery) distinguishes it from siblings like setup_status (checking status) and setup_save_pat (saving a token). No ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context ('for setup or recovery') and specifies prerequisites (permission to read browser credentials, user logged into Figma). It does not explicitly mention when not to use it or compare with alternatives, but given the sibling tools, the use case is clear. Slightly more explicit exclusion would make it a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.

ParametersJSON Schema

Name	Required	Description	Default
`pat`	Yes	Figma Personal Access Token

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No
`result`	No

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=false and destructiveHint=false, which are consistent with the description's 'save' action. The description adds behavioral context beyond annotations: it validates the PAT, saves it, and rejects mismatched accounts. This provides useful operational details that an agent needs to know.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler. It front-loads the core action, then provides an important security-relevant alternative and a rejection condition. Every sentence adds value, making it efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with an output schema present, the description covers the essential purpose, usage guidance, and a behavioral constraint. It doesn't explain the output format (covered by the output schema) or prerequisites like having a saved browser account, but those are either implicit or handled elsewhere. Overall, it is complete enough for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 100% of the parameter 'pat' with a clear description ('Figma Personal Access Token'). The description adds minimal extra meaning—only that it is 'already supplied by the user,' which is more about usage context than parameter semantics. Since schema coverage is high, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action: 'Validate and save a PAT already supplied by the user.' It specifies the resource (PAT) and includes a rejection condition ('Rejects a PAT belonging to a different saved browser account'), making the purpose unambiguous and distinct from sibling tools like setup_status or setup_select_account.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises an alternative method: 'Prefer local figmanage login --pat-only to keep tokens out of chat.' This gives a clear when-not-to-use instruction. However, it does not explicitly contrast with the sibling tools (setup_status, setup_extract_cookies, setup_select_account), but those are not competing alternatives for saving a PAT, so the guidance is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.

ParametersJSON Schema

Name	Required	Description	Default
`account_index`	Yes	Account number returned by setup_extract_cookies

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No
`result`	No

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses specific behaviors: it validates and saves a session, preserves the PAT for the same account, and may prompt the user when selection is ambiguous or changes the existing account. This adds meaningful context about side effects and user interaction without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences, front-loading the core action first, then providing decision rules and a key note on PAT preservation. Every sentence adds value with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and an output schema, the description covers the action, the precondition (after setup_extract_cookies), the decision rule for asking vs. proceeding, and the PAT preservation behavior. It lacks explicit error handling details, but the output schema likely covers return values, making it sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter account_index is fully described in the schema with its source (returned by setup_extract_cookies). The tool description does not add additional meaning beyond that, so it meets the baseline for full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action: validate and save a browser session after setup_extract_cookies. It identifies the resource (browser session) and the sequencing relative to a sibling, making its purpose unambiguous and distinct from setup_status, setup_extract_cookies, and setup_save_pat.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit guidance on when to use it: after setup_extract_cookies, and includes a decision rule for when to ask the user (ambiguous selection or account change) versus using the recommended account silently. It does not explicitly contrast with setup_save_pat, though it mentions PAT preservation, which could overlap, so it is not fully exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No
`result`	No

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, but the description adds meaningful behavioral context: it explicitly states the tool does not read browser credentials or change settings, and mentions a retry behavior for admin access detection. This goes beyond what annotations alone convey, helping the agent understand side-effect boundaries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: the first states the core function, the second gives usage timing, and the third clarifies limitations. The most important information is front-loaded, and there is no redundant or filler language.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless tool with a readOnly hint, an output schema, and three clear usage triggers, the description is complete. It covers purpose, when to use it, and what it avoids doing. The existence of an output schema means detailed return values do not need to be spelled out in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema fully covers this by defining an empty properties object. Per the baseline for 0-param tools, the description need not explain parameters. It instead focuses on purpose and behavior, which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Check live authentication, retry admin access detection, and get structured next actions.' This clearly identifies the tool as a diagnostic/status tool and differentiates it from siblings like setup_extract_cookies or setup_save_pat, which perform credential operations rather than status checks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage triggers are given: 'Use before setup, after an authentication error, or when expected tools are missing.' This gives clear context for when to invoke the tool. It does not explicitly list sibling alternatives, but the closing disclaimer about not reading credentials or changing settings implies when other tools would be appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

4 tool updatesv1.5.0Sep 25, 2026

Changedsetup_extract_cookies2 fields changed

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "result": {}
+  },
+  "type": "object"
+}

Changedsetup_save_pat2 fields changed

changedInput schema / properties / pat / description

Previous value: -"Figma Personal Access Token (starts with figd_)"New value: +"Figma Personal Access Token"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "result": {}
+  },
+  "type": "object"
+}

Changedsetup_select_account2 fields changed

changedInput schema / properties / account_index / description

Previous value: -"Account number from the list returned by setup_extract_cookies"New value: +"Account number returned by setup_extract_cookies"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "result": {}
+  },
+  "type": "object"
+}

Changedsetup_status2 fields changed

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "result": {}
+  },
+  "type": "object"
+}

4 tool updatesv1.4.2Aug 21, 2026
- First observedsetup_extract_cookies
- First observedsetup_save_pat
- First observedsetup_select_account
- First observedsetup_status

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored 2026-09-25 10:00 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

ActivityNo data

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

Figma MCP ServerOAuth
com.figma.mcp
The Figma MCP server brings Figma design context directly into your AI workflow.
Developer Tools Content Management Systems
32,053
ClawLinkOAuth
dev.claw-link
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
App Automation Workplace & Productivity
24
mcp-serverOAuth
com.niftypm
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Project Management Communication File Systems
2
anotherai
dev.anotherai
MCP server for building and testing AI agents with multi-model experimentation and insights.
Agent Orchestration Autonomous Agents Testing & QA Tools
2

Related MCP Servers

Figma API MCP Server
App Automation Content Management Systems Developer Tools
huazhengwang
F
license
Not graded
quality
D
maintenance
An MCP (Multi-Agent Conversation Protocol) Server that enables interaction with the Figma REST API, auto-generated using AG2's MCP builder.
Updated a year ago (2025-07-07 17:47 UTC)
1
-
figma-pilot
Developer Tools App Automation Software Architecture
youware-labs
A
license
Not graded
quality
C
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.
Updated 8 months ago (2026-01-29 14:10 UTC)
8 npm
106
MIT
figmind
Design Tools AI & Machine Learning
guhcostan
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.
Updated 7 months ago (2026-03-07 22:38 UTC)
MIT
figma-mcp-write-server
Design Tools Developer Tools
oO
F
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.
Updated 10 months ago (2025-11-25 16:29 UTC)
23
-