Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for frontend and design-system teams that want a higher-bandwidth path from Figma into Cursor, Claude Code, or Codex when shipping UI work with agent help.
Where this stands now
grab/cursor-talk-to-figma-mcp ranks #210 of 2770 tracked Radar items by composite score (8.4 against a section median of 4.9). The section currently carries 1659 Bronze, 645 Gold, 466 Silver. RepoRadar has retained observations for this record since 2026-07-01 (94 days in the current window). Signal extremes versus the section: momentum at the 83th percentile; novelty at the 83th percentile.
Who should use it
Who should skip it
Skip grab/cursor-talk-to-figma-mcp unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
grab/cursor-talk-to-figma-mcp is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-07-01; the source record was last checked on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, grab/cursor-talk-to-figma-mcp is strongest on workflow potential (9.9) and open-source/build quality (8.4) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The grab/cursor-talk-to-figma-mcp record combines a 8.4/10 composite score with separate popularity (1.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It can read private Figma files and modify designs programmatically, so initial trials should stay in a sandbox workspace with a throwaway design file; The local MCP plus plugin plus websocket setup widens the trust surface, so teams should review the bridge before pointing it at production design systems.