Uxloom vs Figwright

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
U
Uxloom
uxloom-dev
📐 Architecture & Design
F
Figwright
awdr74100
📐 Architecture & Design
SummaryAgent-native UI/UX design validation: model user journeys as state machines and prove what AI-generated screens are missing (unreachable states, missing empty/loading/error states, WCAG contrast, touch targets, localization overflow) before code exists — then verify the code implements the contract. Deterministic CI gates (uxloom check, uxloom audit), one-command setup (npx uxloom init).Bidirectional Figma server over a local WebSocket relay: turn a selection into framework-aware code (reusing your components and tokens), or author frames, text, styles, variables, and whole screens back onto the canvas. 92 tools, any MCP client, no Dev Mode seat or paid tier.
Quality signal25/100 (Emerging)24/100 (Emerging)
Install pathnpx · highnpx · low
Engagement 2 0 0 2 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView UxloomView Figwright
More alternatives to UxloomMore alternatives to FigwrightArchitecture & Design categoryCanonical compare URL

Other servers like Uxloom