figma-ui-mcp

MCPattested
v2.5.29TranHoaiHungMITUpdated 10d agonpmGitHub

Claude Code to Figma — Bidirectional MCP bridge. AI draws UI on Figma canvas, reads designs back. Works with Claude, Cursor, VS Code, Windsurf, Antigravity. No API key needed.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
329Downloads/wk
264GitHub stars
48Forks
10d agoLast update
Package
AuthorTranHoaiHung
LicenseMIT
Version2.5.29
Sourcenpm+mcp-registry
npmfigma-ui-mcp
GitHubTranHoaiHung/figma-ui-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 2c8644b
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · 1 privileged
Security scan✓ Cleanv2.5.29 · todayHow well does this scan work?
EvalsNone
IndexedOct 17, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · 1 privileged
Statically extracted from the published packagev2.5.29 · 8h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

figma_statusCheck whether the Figma plugin bridge is connected.

Check whether the Figma plugin bridge is connected.

No input schema was published for this tool.

figma_writeprivilegedExecute JavaScript code to CREATE or MODIFY designs in Figma.

Execute JavaScript code to CREATE or MODIFY designs in Figma.

No input schema was published for this tool.

figma_readREAD design data from Figma — extract node trees, colors, typography, spacing, and screenshots.

READ design data from Figma — extract node trees, colors, typography, spacing, and screenshots.

No input schema was published for this tool.

figma_docsGet the API reference and design rules for figma_write.

Get the API reference and design rules for figma_write.

No input schema was published for this tool.

figma_rulesGenerate a design system rule sheet from the current Figma file — aggregates color tokens,

Generate a design system rule sheet from the current Figma file — aggregates color tokens,

No input schema was published for this tool.

5 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Claude Code to Figma — Bidirectional MCP bridge. AI draws UI on Figma canvas, reads designs back. Works with Claude, Cursor, VS Code, Windsurf, Antigravity. No API key needed.

Keywords
figmamcpmodel-context-protocolclaudeclaude-codecursorwindsurfvscodeantigravityaidesignpluginfigma-pluginui-generationfigma-mcpai-to-figmaclaude-to-figmacode-to-figmadesign-to-codefigma-bridgefigma-automation
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-21 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in design tools