figma-context-mcp

Figma Context MCP Server

Figma layouts, components, and tokens become context for coding agents through figma-context-mcp. It serves developers and design-system teams with extraction, documentation, token comparison, and accessibility checks.

Server facts

figma-context-mcp

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
28
Last commit
Data as of

Tags

  • Figma
  • ai agents
  • design systems

Overview

Figma files provide the starting point for figma-context-mcp’s design-to-code workflow. Developers can share a file, frame, or group link with a configured agent such as Cursor, which retrieves layout and styling context through the server. Component analysis describes variants, relationships, properties, and implementation patterns, while image retrieval downloads SVG or PNG assets by node ID. Separate tools extract color, typography, spacing, and effect tokens into JSON and produce Markdown design-system documentation in a chosen directory. Direct retrieval of Figma variables requires an Enterprise plan; token generation also offers deduced variable analysis for non-Enterprise users.

For ongoing design-system maintenance, teams can compare token sets or Figma files to inspect additions, removals, and modifications. Validation examines conventions such as naming, typography scales, and spacing patterns, while accessibility checks flag concerns involving contrast, text size, and touch targets. Token migration supports Tailwind, CSS Variables, Style Dictionary, and Figma Tokens outputs. A separate synchronization check compares design tokens against implementation tokens in JSON, JavaScript, or TypeScript files, helping teams locate discrepancies without treating the check as a guarantee of alignment.

figma-context-mcp setup notes

  • figma-context-mcp records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers