Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.neozhehan/figma-edit-mcp

NPM · FIGMA-EDIT-MCP · SCANNED SEP 21

Programmatically read, create, and modify Figma designs via MCP.

Available components

npm · figma-edit-mcp 89
0 this week 89 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects ws 8.20.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 84 of 189 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to neozhehan/figma-edit-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 47 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6389 tokens (~127/item across 50 items; 45 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.neozhehan/figma-edit-mcp server?

io.github.neozhehan/figma-edit-mcp runs locally as an npm package, launched with npx -y figma-edit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · figma-edit-mcp

# add to Claude Code
claude mcp add neozhehan-figma-edit-mcp -- npx -y figma-edit-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "neozhehan-figma-edit-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figma-edit-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "neozhehan-figma-edit-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figma-edit-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add neozhehan-figma-edit-mcp -- npx -y figma-edit-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neozhehan-figma-edit-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "figma-edit-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add neozhehan-figma-edit-mcp --command npx --arg -y --arg figma-edit-mcp
# ~/.hermes/config.yaml
mcp_servers:
  neozhehan-figma-edit-mcp:
    command: "npx"
    args: ["-y", "figma-edit-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "neozhehan-figma-edit-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "figma-edit-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add neozhehan-figma-edit-mcp -t stdio -c npx -a -y figma-edit-mcp
// mcp.json
{
  "mcpServers": {
    "neozhehan-figma-edit-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "figma-edit-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/figma-edit-mcp@2.3.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo neozhehan/figma-edit-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/neozhehan/figma-edit-mcp/.github/workflows/publish.yml@refs/tags/v2.3.3
Rekor log index 2339133716
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:bc99ac7e913f4ad3f8f781f7f82c385f44d621ade3cca668274b72d630c8e52ea94cf0ad3405fed158216af0e811c16ec5f2ae1d07f2ae3438bfb7945

Background: How many MCP packages publish verified provenance →

Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-5v7r-6r5c-r473 CVE-2026-31808 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-58qx-3vcg-4xpx CVE-2026-45736 medium CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N yes
GHSA-96hv-2xvq-fx4p CVE-2026-48779 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 189 packages
Packages resolved 189
Deprecated 1
Stale 84
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 45 exposed · ~6,181 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
variable_list ~140

List local variables/collections, or detailed info for specific variable ids; optionally scan for consumers. Document consumer scans isolate page failures and report them in `coverage`; page-scoped failures return their structured error directly.

NameTypeReqDescription
includeConsumersstring–Only used when variableId is provided; ignored otherwise. 'page' scans a specific page, requiring pageId. 'document' scans all pages (streams progress page-by-page).
pageIdstring–The page ID to scan for consumers when includeConsumers is 'page'.
variableIdarray–Optional array of variable IDs to retrieve detailed information for. If omitted, lists all local variables.
NameTypeReqDescription
collectionsarray–List of variable collections (list-all mode only)
coverage––Page-scan coverage; partial read data remains usable when complete is false
errorobject––
missingIdsarray–Requested variable IDs that did not resolve (lookup mode only; omitted when none)
variablesarray–List of variables — present in both list-all and lookup modes (each may carry nodeConsumers/styleConsumers/aliasConsumers when includeConsumers is set)

No examples provided.

variable_manage ~305

Create collections and variables and set their values/aliases (create/update router). UPDATE_VARIABLE requires `currentVariableName`. CREATE_VARIABLE requires `collectionName` and `scopes`.

NameTypeReqDescription
actionstringyesAction type
collectionIdstring–Collection ID (for CREATE_VARIABLE)
collectionNamestring–REQUIRED for CREATE_VARIABLE — the parent collection's exact name, passed back verbatim from `variable_list`
currentVariableNamestring–REQUIRED for UPDATE_VARIABLE — the variable's **current exact** name, passed back verbatim from `variable_list`
descriptionstring–Description (for UPDATE_VARIABLE)
modeIdstring–Mode ID (for UPDATE_VARIABLE value setting)
modeNamestring–Optional initial mode name for CREATE_COLLECTION. Must be non-empty when supplied; omit it to keep the collection's native default mode name.
namestring–Name for collection/variable creation or variable update. Must be non-empty when supplied. It is required for CREATE_COLLECTION and CREATE_VARIABLE; omit it only on UPDATE_VARIABLE to leave the curre…
scopesarray–REQUIRED for CREATE_VARIABLE — variable scopes. ALWAYS set explicitly on create; omit on update to leave unchanged.
typestring–Variable type (for CREATE_VARIABLE)
value––Value for the variable (or alias) (for CREATE or UPDATE)
variableIdstring–Variable ID (for UPDATE_VARIABLE)
NameTypeReqDescription
errorobject––
idstring–ID of the collection or variable
namestring–Name of the collection or variable

No examples provided.

view_navigate ~36

Navigate the editor view to a page or node(s).

NameTypeReqDescription
idsarrayyesArray of page or node IDs to navigate to
NameTypeReqDescription
countnumber–Number of selected nodes
errorobject––
messagestring–Status message
pageIdstring–The ID of the target page transitioned to
pageNamestring–The name of the target page transitioned to
selectedNodesarray–List of selected nodes
successboolean–Whether navigation was successful

No examples provided.

Common questions

What is the io.github.neozhehan/figma-edit-mcp server?

io.github.neozhehan/figma-edit-mcp is listed in the public MCP registry as io.github.neozhehan/figma-edit-mcp. Programmatically read, create, and modify Figma designs via MCP. This page covers its npm package (figma-edit-mcp).

Is the io.github.neozhehan/figma-edit-mcp server safe to use?

io.github.neozhehan/figma-edit-mcp scores 89 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.neozhehan/figma-edit-mcp server expose?

io.github.neozhehan/figma-edit-mcp exposes 45 tools: page_info, node_info, node_transform, node_rename, node_delete, and 40 more. Their descriptions and schemas cost roughly 6,181 tokens of context every time the server is loaded.

Is the io.github.neozhehan/figma-edit-mcp server still maintained?

io.github.neozhehan/figma-edit-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.neozhehan/figma-edit-mcp server under?

io.github.neozhehan/figma-edit-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.