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.

Figma Proxy MCP

NPM · FIGMA-PROXY-MCP

Figma → code: tokenized IR, PNG renders and SSIM/pixel visual diff to verify builds.

Available components

65 Trust /100

Last scanned (15 hours ago)

Scores higher than 37% of npm servers

Category Design and Media

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 23 of 70 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1796 tokens (~199/item across 9 items; 9 tools + 0 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 50

    First indexed and scored.

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 Nov 2026 · Analysed npm/figma-proxy-mcp@1.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 70 packages
Packages resolved 70
Stale 23
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,484 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
export_svg ~141

Export a specific Figma node as SVG and optionally save it

NameTypeReqDescription
fileIdstringyesFigma file ID
fileNamestring–Custom filename for saved SVG (optional)
nodeIdstringyesNode ID to export as SVG
outputDirstring–Output directory for saved SVGs (default: $FIGMA_PROXY_SVG_DIR or ./exported-svgs relative to the server working directory; pass an absolute path to be explicit)
saveboolean–Whether to save the SVG to disk (default: false)
scalenumber–Scale factor for export (default: 1)

No output schema declared.

No examples provided.

get_cached_components ~17

Get previously fetched Figma components data

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_component_by_name ~35

Get a specific Figma component by name from cached data

NameTypeReqDescription
namestringyesName of the component to find

No output schema declared.

No examples provided.

get_figma_component ~556

Get a Figma node by URL. Returns a deterministic, pruned + tokenized + componentized IR with a :root{} CSS-variable block, a Tailwind theme, and a component registry. Colors/spacing/fonts are already resolved to $--var references — the caller does NOT need to re-match raw RGBA against :root. For large sections, call with summary:true FIRST to get a compact { cssVars, tailwindTheme, registry, sections[] } object (top-level children with bounding boxes) WITHOUT the full node tree; this replaces manual get_figma_file decomposition. Then fetch individual sections (optionally with maxDepth) to build them.

NameTypeReqDescription
componentizeboolean–Cluster repeated nodes into a component registry with variant axes and named text styles. Default true.
figmaUrlstringyesFull Figma URL to a specific node (e.g., https://www.figma.com/design/{fileId}/...?node-id={nodeId})
formatstring–(non-summary) IR shape. "nested" (default) = full annotated tree. "flat" = a flat array of compact node records (render fields only, coords RELATIVE to the root frame) — much smaller and machine-read…
leanboolean–Omit the global blocks (CSS vars, Tailwind theme, component registry) that are identical on every call. Pass true on per-section fetches AFTER the summary call to avoid re-sending ~15KB of duplicated…
maxDepthnumber–Cap the IR tree depth (e.g. 3-4) to keep a large section compact without manual decomposition. Omit for full depth.
minFreqnumber–Minimum occurrences for a value to become a design token during tokenization (default 2).
pruneboolean–Run the deterministic noise-pruning pass (collapse decorative wrappers, drop invisible/zero-size nodes). Default true; set false for raw IR (debug).
summaryboolean–When true, return a compact summary (component meta, CSS vars, Tailwind theme, component registry, and top-level sections with bounding boxes) instead of the full annotated IR tree. Recommended first…
tokenizeboolean–Run frequency-analysis tokenization: emit :root CSS vars + Tailwind theme and replace raw color/spacing/font values in the IR with $--var references. Default true.

No output schema declared.

No examples provided.

get_figma_file ~49

Get Figma file data by file ID and transform it for development

NameTypeReqDescription
fileIdstringyesFigma file ID (from the URL: figma.com/file/{fileId}/...)

No output schema declared.

No examples provided.

list_svg_cache ~15

List all cached SVG exports

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

migrate_all_svgs ~85

Automatically find and export all SVG icons from a Figma file

NameTypeReqDescription
fileIdstringyesFigma file ID to migrate SVGs from
outputDirstring–Output directory for exported SVGs (default: $FIGMA_PROXY_SVG_DIR or ./exported-svgs relative to the server working directory; pass an absolute path to be explicit)

No output schema declared.

No examples provided.

render_node_png ~126

Export a specific Figma node as PNG and return base64-encoded image data

NameTypeReqDescription
figmaUrlstring–Full Figma URL to a specific node (e.g., https://www.figma.com/design/{fileId}/...?node-id={nodeId})
fileIdstring–Figma file ID (alternative to figmaUrl)
nodeIdstring–Node ID to export (alternative to figmaUrl, use colon format: 12:34)
scalenumber–Scale factor for PNG export (default: 2)

No output schema declared.

No examples provided.

verify_render ~460

Visual verification (MEASUREMENT ONLY): render an HTML file with headless Chromium INSIDE this server (does NOT use the user's own browser) and compare it to the Figma design PNG. Returns SSIM (0-1, higher = closer), pixel-diff %, and clustered diff regions (bounding boxes of disagreement, in logical px). Provide the reference PNG via figmaUrl (auto-fetched), figmaPngPath, or figmaPngBase64. Use after generating HTML to objectively check fidelity, then fix only the reported regions — this tool never changes code. Requires Playwright Chromium: `npx playwright install chromium`.

NameTypeReqDescription
bgarray–Background [r,g,b] to flatten transparent reference-PNG pixels onto before comparing. Default [255,255,255]. For dark designs pass the real background (e.g. [13,17,23]) — otherwise transparent areas…
cliparray–Optional [x,y,w,h] in CSS/logical px to compare ONLY the content area. Use it to exclude dead margins / parent-canvas background that the isolated frame cannot reproduce (that noise otherwise dominat…
figmaPngBase64string–Alternative: base64 of the reference PNG.
figmaPngPathstring–Alternative to figmaUrl: local path to an already-saved reference PNG.
figmaUrlstring–Figma node URL — reference PNG fetched automatically at the given scale.
frameWidthnumberyesFigma frame width in CSS px (e.g. 1440 or 1920). HTML is rendered at this width.
htmlPathstringyesAbsolute path to the generated .html file to render.
outDirstring–Directory for the diff image (default: $FIGMA_PROXY_VERIFY_DIR or <os temp dir>/figma-proxy-mcp/verify-out).
scalenumber–Device scale factor for render and reference (default 2 — match render_node_png).
thresholdnumber–SSIM pass threshold (default 0.95).

No output schema declared.

No examples provided.

Install

How do I install the Figma Proxy MCP server?

Figma Proxy MCP runs locally as an npm package, launched with npx -y figma-proxy-mcp --stdio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

npm · figma-proxy-mcp

# add to Claude Code
claude mcp add semmargl-figma-proxy-mcp -- npx -y figma-proxy-mcp --stdio
Common questions

What is the Figma Proxy MCP server?

Figma Proxy MCP is listed in the public MCP registry as io.github.Semmargl/figma-proxy-mcp. Figma → code: tokenized IR, PNG renders and SSIM/pixel visual diff to verify builds. This page covers its npm package (figma-proxy-mcp).

Is the Figma Proxy MCP server safe to use?

Figma Proxy MCP scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Figma Proxy MCP server expose?

Figma Proxy MCP exposes 9 tools: get_figma_file, get_figma_component, export_svg, render_node_png, migrate_all_svgs, and 4 more. Their descriptions and schemas cost roughly 1,484 tokens of context every time the server is loaded.

Is the Figma Proxy MCP server still maintained?

Figma Proxy MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Figma Proxy MCP server under?

Figma Proxy 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.

What did VerifyMCP test on the Figma Proxy MCP server?

VerifyMCP ran 15 checks on Figma Proxy MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Figma Proxy MCP: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.