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

io.github.MananSingh2001/figma-react

NPM · @MANANSIINGH/FIGMA-REACT-MCP-SERVER · SCANNED AUG 3

An MCP server that converts Figma designs into React code.

Available components

npm · @manansiingh/figma-react-mcp-server 60
+20 this week 60 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (107 of 108), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (107 of 108), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 88 tokens (~88/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @manansiingh/figma-react-mcp-server

# add to Claude Code
claude mcp add manansingh2001-figma-react -- npx -y @manansiingh/figma-react-mcp-server
# add to Codex CLI
codex mcp add manansingh2001-figma-react -- npx -y @manansiingh/figma-react-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "manansingh2001-figma-react": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@manansiingh/figma-react-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add manansingh2001-figma-react --command npx --arg -y --arg @manansiingh/figma-react-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  manansingh2001-figma-react:
    command: "npx"
    args: ["-y", "@manansiingh/figma-react-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "manansingh2001-figma-react": {
      "command": "npx",
      "args": [
        "-y",
        "@manansiingh/figma-react-mcp-server"
      ]
    }
  }
}
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.

  • 2 Aug 26 +60
    • Provenance: unverified → fail ▼ security
    • Known CVEs: unverified → partial ▲ security
    • Install scripts: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • License: unverified → fail ▼ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • Schema quality: unverified → good ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 1 Aug 26 −1
    • Dependency health: partial → unverified ▼ functional
  • 31 Jul 26 −39
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 40

    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 3 Aug 2026 · Analysed npm/@manansiingh/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 107 packages

107 packages in the resolved dependency tree · 107 deprecated · 32 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 1 exposed · ~88 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.

Tool Tokens
generate_react_component ~88

Fetch a specific Figma node by ID and convert its design tokens to a production-ready React component string.

NameTypeReqDescription
figmaTokenstringyesPersonal Access Token for the Figma API
fileKeystringyesThe unique key of the Figma file (from the URL).
nodeIdstringyesThe ID of the requested Figma node from the design file.

No output schema declared.

No examples provided.