io.github.TranHoaiHung/figma-ui-mcp
NPM · FIGMA-UI-MCP
Bidirectional Figma MCP — AI draws UI on Figma canvas, reads designs back
Available components
Last scanned (22 hours ago)
Scores higher than 94% of npm servers
Category Design and Media
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to TranHoaiHung/figma-ui-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1370 tokens (~274/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "figma_write" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 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
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.
- 4 Nov 26 0
- Package version: 2.5.29 → 2.5.30 functional
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 +25
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 26 Oct 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 2.5.29 → 2.5.30 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 −1
- Stability: pass → 0.93 functional
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 4 Nov 2026 · Analysed npm/figma-ui-mcp@2.5.30
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 | TranHoaiHung/figma-ui-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/TranHoaiHung/figma-ui-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3481717843 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c23c2cb94dd7c805f8e14b39f2b5fc18ad7ad498ee187461040bf3ccceb1e25ead1af95fcad8f24b59fe1e4760e254124b98482c70673549dce99ea08 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
figma_docs ~199
Get the API reference and design rules for figma_write. Call with no args first — returns quick-start guide + critical rules. Then load specific sections as needed: section='rules' (design principles, token rules, layer order, component-first), section='layout' (auto-layout, button/card/badge/progress/mobile rules), section='api' (create/modify/delete/clone/batch/read operations + workflow), section='tokens' (variables, multi-mode, paint styles, text styles), section='icons' (loadImage, loadIcon, loadIconIn, icon libraries, coloring, sizing). Always call figma_docs BEFORE any figma_write code.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Which section to load. Omit (or null) for quick-start + critical rules. Load layout before any auto-layout work. Load api for full operation reference. Load tokens for variable/multi-mode work. Load… |
No output schema declared.
No examples provided.
figma_read ~681
READ design data from Figma — extract node trees, colors, typography, spacing, and screenshots. Use to understand an existing design before generating code, or to inspect what's on the canvas.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | Tree depth for get_design/get_selection. Number (default 10) or 'full' for unlimited. Higher = more detail but larger output. |
| detail | string | – | Detail level for get_design/get_selection: 'minimal' (~5% tokens), 'compact' (~30%), 'full' (default, 100%). Use minimal for large files. |
| format | string | – | Image format for export_image: 'png' (default) or 'jpg'. |
| includeHidden | boolean | – | Include invisible nodes (visible:false) in results. Default false — hidden layers are skipped to reduce noise. |
| nodeId | string | – | Target node ID (optional — omit to use current selection). |
| nodeName | string | – | Target node name (alternative to nodeId). |
| operation | string | yes | ── Design-to-code (use these for code generation) ── get_design_context: AI-optimized payload for a node — flex layout, token-resolved colors, typography with style names, component instances with va… |
| scale | number | – | Export scale for screenshot (default 1). |
| sessionId | string | – | Target a specific Figma file/tab when multiple are connected. Omit to auto-select. |
No output schema declared.
No examples provided.
figma_rules ~117
Generate a design system rule sheet from the current Figma file — aggregates color tokens, typography styles, variables (all modes), and component catalog into a single markdown block. Equivalent to official Figma MCP's create_design_system_rules. Call once at the start of a design-to-code session to give the AI full context: what tokens to use, what text styles exist, which components are available. Re-run when the design system changes.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | – | Target a specific Figma file/tab. Omit to auto-select. |
No output schema declared.
No examples provided.
figma_status ~34
Check whether the Figma plugin bridge is connected. Always call this first to confirm the plugin is running before any other tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
figma_write ~339
Execute JavaScript code to CREATE or MODIFY designs in Figma. ⚠️ MANDATORY: Call figma_docs BEFORE writing any design code. Skipping figma_docs causes hardcoded colors, wrong sizing, broken layouts, and low-quality UI. Use the `figma` proxy object — all methods return Promises, use async/await. Operations: create, modify, delete, clone, group, ungroup, flatten, resize, set_selection, set_viewport, batch (multiple ops in one call). Design Tokens: createVariableCollection, createVariable, setVariableValue, addVariableMode, renameVariableMode, removeVariableMode, applyVariable, setFrameVariableMode, clearFrameVariableMode, createPaintStyle, createTextStyle, createComponent. Prototyping: setReactions, getReactions, removeReactions (click/hover/press → navigate/overlay/swap with Smart Animate transitions). Scroll: setScrollBehavior (overflowDirection: NONE/HORIZONTAL/VERTICAL/BOTH). Variants: setComponentProperties, swapComponent, getComponentProperties. Component property definitions (master-side, required for instance text overrides to recalc auto-layout): addComponentProperty (TEXT/BOOLEAN/INSTANCE_SWAP), bindComponentPropertyToText, removeComponentProperty. The code runs in a sandboxed VM: no access to require, process, fs, fetch, or network.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JavaScript using figma.create(), figma.modify(), figma.setPage(), etc. |
| sessionId | string | – | Target a specific Figma file/tab when multiple are connected. Omit to auto-select. |
No output schema declared.
No examples provided.
How do I install the io.github.TranHoaiHung/figma-ui-mcp server?
io.github.TranHoaiHung/figma-ui-mcp runs locally as an npm package, launched with npx -y figma-ui-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-ui-mcp
claude mcp add tranhoaihung-figma-ui-mcp -- npx -y figma-ui-mcp
What is the io.github.TranHoaiHung/figma-ui-mcp server?
io.github.TranHoaiHung/figma-ui-mcp is listed in the public MCP registry as io.github.TranHoaiHung/figma-ui-mcp. Bidirectional Figma MCP, AI draws UI on Figma canvas, reads designs back. This page covers its npm package (figma-ui-mcp).
Is the io.github.TranHoaiHung/figma-ui-mcp server safe to use?
io.github.TranHoaiHung/figma-ui-mcp scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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.TranHoaiHung/figma-ui-mcp server expose?
io.github.TranHoaiHung/figma-ui-mcp exposes 5 tools: figma_status, figma_write, figma_read, figma_docs, figma_rules. Their descriptions and schemas cost roughly 1,370 tokens of context every time the server is loaded.
Is the io.github.TranHoaiHung/figma-ui-mcp server still maintained?
io.github.TranHoaiHung/figma-ui-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.TranHoaiHung/figma-ui-mcp server under?
io.github.TranHoaiHung/figma-ui-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.