claude-talk-to-figma-mcp and figma-unified-mcp
These are competitors offering overlapping MCP-based Figma integration capabilities, with A focusing on design analysis and modification while B emphasizes broader design creation and token management, requiring users to choose based on feature priorities rather than use them together.
About claude-talk-to-figma-mcp
arinspunk/claude-talk-to-figma-mcp
A Model Context Protocol (MCP) that allows Claude Desktop and other AI tools (Claude Code, Cursor, Antigravity, etc.) to read, analyze, and modify Figma designs
Implements a WebSocket-based plugin architecture that bridges Figma Desktop with MCP servers, enabling real-time bidirectional communication without requiring a Dev Mode license. Supports design analysis (contrast audits, component scanning), bulk modifications (colors, typography, auto-layout), and code generation (React/Vue/SwiftUI components with design tokens). Integrates across multiple AI agents including Claude Desktop, Cursor, Windsurf, and VS Code extensions via configurable MCP server setup.
About figma-unified-mcp
sso-ss/figma-unified-mcp
Describe it, and it appears in Figma. 106 tools, 14 agent skills. Read, create, edit designs & manage tokens via Claude, Cursor, or any MCP client. Open source.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work