awdr74100/figwright: AI tool review & score

Score7.7

Popularity1.0

Risklow

TierSilver

Score breakdown

Usefulness8.0

Novelty9.0

Momentum7.0

Maturity5.6

Open-source/build8.4

Evidence7.2

Workflow potential9.2

Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for frontend engineers, designers, and design-system teams who want an AI agent that can both read a Figma design and write back to the canvas — not just look at a screenshot and emit code the user has to rewrite. The official Figma MCP server (Dev Mode) is gated behind a paid seat; Figwright is the open alternative that ships 95 tools and the bidirectional surface, with the read path groun

Who should use it

Frontend engineers who want an AI agent to read a Figma selection and emit framework-aware code that drops into the real codebase (matches the user's framework, styling system, components, tokens, icons) instead of generic markup the user has to rewriteDesigners and design-system teams who want an AI agent to write back to the Figma canvas — author new screens, iterate on a design, fill in variables, create components — from inside the same MCP client that reads themAnyone who has hit the official Figma Dev Mode MCP paywall and wants the bidirectional surface (95 tools, not the read-only subset) without paying for a Figma Dev Mode seatTeams where a CLI agent and an IDE agent both need to drive the same Figma file — the leader-election pattern lets them share one plugin connection without stepping on each otherAnyone who needs MCP server + Claude Code skill + Codex skill + local WebSocket transport (no cloud round-trip) from one repo, with CI + tests + CHANGELOG + a published npm package — production hygiene, not a demoAnyone who needs the Figma plugin to ride out dropped sockets — the transport is built for unreliable local networks and the leader-election pattern heals when the leader disconnects

Who should skip it

Consider awdr74100/figwright lower priority if you already have a working solution in this category.

About this signal

awdr74100/figwright is tracked by RepoRadar as a bidirectional figma mcp server ( in the MCP Servers section. It was first seen on 2026-07-04 and last updated on 2026-07-04. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, awdr74100/figwright is strongest on workflow potential (9.2) and novelty (9.0) and weakest on maturity (5.6) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned awdr74100/figwright a composite score of 7.7 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

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

Risk label is still being reviewed from the captured evidence. Treat the item as unknown-risk until you review the linked source, permissions, setup path, and data access.

Evidence links

github.com

Closest alternatives / related signals

mcpmcp-serverfigmadesign-to-codebidirectionalcode-generationclaude-codecursor