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.
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.
Catch bad animations before they ship. 13 deterministic checks on the live page (duration, easing, stagger, exits, reduced-motion, touch-gated hover) with no API key or LLM, plus optional vision-LLM UX review across viewports. Install via NPM: npx -y motionlint mcp
Quality signal
52/100 (Fair)
41/100 (Fair)
Install path
npx · high
npx · high
Engagement
3 0 0 435
0 0 0 0
Tools
Local WebSocket relay connecting MCP clients to a Figma pluginBidirectional design-code synchronization with 92+ tools for reading and writingProvider-first code generation detecting real framework and styling systemSupports multiple MCP clients with leader election and session resumeOpen source with extensible installable skillsNo Figma Dev Mode seat or paid tier required
