# figmanage Let agents manage your Figma workspace. 102 tools for seats, teams, offboarding, and cleanup. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the package rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 1.5.0 - **Author:** io.github.dannykeane - **License:** Unknown - **npm:** figmanage - **Source:** https://github.com/dannykeane/figmanage - **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport) ## Trust 60/100 (B), scored on the package rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-09-21T10:39:32.145Z - **Version scanned:** 1.5.0 - **CVEs:** none found by OSV at scan time ## Tools 40 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `library_usage` — Team-level library adoption metrics. Shows how a published library is used across teams. - `component_usage` — Per-file component usage analytics. Shows which files use a specific component. - `list_branches` — List branches of a file. - `create_branch` — Create a branch from a file. - `delete_branch` — Archive (delete) a branch. Uses the branch file key from list_branches. - `list_comments` — List comments on a file. Returns comment text, author, timestamps, and thread structure. - `post_comment` — Post a comment on a file. Optionally pin to a specific node or reply to an existing comment. - `delete_comment` — Permanently delete a comment. For top-level comments, the entire thread is removed. Cannot be undone. - `list_comment_reactions` — List emoji reactions on a comment. - `resolve_comment` — Resolve or unresolve a comment thread. Resolved comments are collapsed in the Figma UI. - `edit_comment` — Edit the text of an existing comment. - `add_comment_reaction` — Add an emoji reaction to a comment. - `remove_comment_reaction` — Remove your emoji reaction from a comment. - `list_file_components` — List components published from a file. Only published library components appear -- local unpublished components are not included. - `list_file_styles` — List styles published from a file. Only published library styles appear. - `list_team_components` — List published components across a team. Pass the cursor from the response's pagination object to fetch the next page. - `list_team_styles` — List published styles across a team. Pass the cursor from the response's pagination object to fetch the next page. - `offboard_user` - `onboard_user` — Invite a user to teams and optionally share files and set seat type. Sends invite emails per team. - `quarterly_design_ops_report` — Org-wide design ops snapshot: seat utilization, team activity, billing, and library adoption over a given period. - `file_summary` — Quick overview of a Figma file. Fetches pages, components, styles, and comment counts in parallel. - `workspace_overview` — Full org snapshot: teams with member/project counts, seat breakdown, and billing summary. - `open_comments` — Aggregated unresolved comments across all files in a project. Checks up to 20 files. - `cleanup_stale_files` — Find files not modified in N days and optionally trash them. dry_run=true (default) previews which files would be trashed without trashing them. Set dry_run=fal - `organize_project` — Move files into a target project in a single batch. Files are moved (not copied) from their current project. - `setup_project_structure` — Create multiple projects in a team from a plan. Optionally set descriptions. - `seat_optimization` — Identify inactive paid seats and calculate potential savings. Fetches members, seat counts, and pricing to find optimization opportunities. - `permission_audit` — Audit permissions across a team or project. Scans files for external editors, open link access, and elevated individual permissions. - `branch_cleanup` — Find stale branches across a project and optionally archive them. dry_run=true (default) previews which branches would be archived. Archives move branch files t - `list_dev_resources` — List dev resources (links, annotations) attached to nodes in a file. Used in Dev Mode. - `create_dev_resource` — Create a dev resource (link/annotation) on a node. Visible in Dev Mode. - `delete_dev_resource` — Delete a dev resource from a file. - `export_nodes` — Export specific nodes from a file as images. Returns temporary URLs (valid ~14 days). - `get_image_fills` — Get download URLs for all images used as fills in a file. - `create_file` — Create a new Figma file in a project. Supports design, whiteboard, slides, sites. - `rename_file` — Rename a Figma file. - `move_files` — Move one or more files to a different project. Supports batch moves. - `duplicate_file` — Duplicate a file. Optionally specify a destination project. - `trash_files` — Move files to trash (recoverable via restore_files). Supports batch operations. - `restore_files` — Restore files from trash. ## Install **Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for. **Cautions** (coverage gaps and advisories — never blocking) - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"figmanage\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"figmanage\"\n ]\n }\n }\n}" ``` ## Blast radius Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine. - Floor 42, ceiling 66 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/figmanage - Install plan: https://forgeregistry.com/api/v1/packages/figmanage/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/figmanage - HTML page: https://forgeregistry.com/registry/figmanage - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.