$ show southleft/figma-console-mcp
This repository is a production-grade Model Context Protocol (MCP) server that bridges AI assistants to Figma. It exposes 100+ MCP tools for reading and manipulating Figma files, variables, components, styles, FigJam boards, Slides, version history, tokens, and accessibility audits. The architecture is dual-mode: a local Node.js server (`src/local.ts`) communicates over stdio to AI clients and via WebSocket to a bundled Figma Desktop Bridge plugin, while a Cloudflare Workers variant (`src/index.ts`) supports cloud sessions with OAuth and a Durable Object WebSocket relay. The Desktop Bridge is the primary data channel, with Figma REST API fallbacks for scenarios where the plugin is unavailable or limited to certain plans. Beyond basic Figma CRUD, the codebase contains substantial engineering investment in design-token synchronization: canonical DTCG-aligned token documents round-trip through parsers and formatters for CSS variables, Tailwind v3/v4, SCSS, TypeScript modules, Style Dictionary, and Tokens Studio. A separate extraction engine (`src/core/extraction/`) mines production codebases for styling conventions and scaffolds design-system packages, while a scoring engine produces weighted design-system health dashboards. These components give the repo a hybrid quality: it is fundamentally an application, but its token pipeline and codebase-analysis subsystems are data-engineering-like assets that could be reused independently. The codebase demonstrates strong engineering practices: strict Zod schemas, consistent tool registration factories, connector abstraction, extensive Jest test coverage, atomic file writes, adaptive response compression, and careful caching/invalidation. However, it also carries meaningful debt: some token parsers are unimplemented stubs, a few files are monolithic (`figma-tools.ts`, `src/local.ts`), local/cloud connector implementations must be kept in sync manually, and some documentation references outdated internal paths. Overall, this is a mature, feature-rich MCP server with several genuinely reusable components for anyone building design-tool pipelines, token bridges, or local process-lifecycle infrastructure.
The LLM identified 5 files worth highlighting for reuse:
Builds a set-aware token index and resolves {path.to.token} references across token sets, with alias chain resolution, cycle detection, and cross-library sentinel handling. Used by every token formatter and parser; can be extracted into any design-token pipeline.
Converts between legacy and 2025.10 DTCG dialects and canonicalizes dimension/color literals, preserving round-trip fidelity for multi-mode design tokens. Self-contained transformation utilities applicable to any token import/export system.
Reserves ports across a bounded range with atomic advertisement files, heartbeat staleness checks, liveness probes, orphan reaping, and oldest-instance eviction. A robust, generic local-daemon lifecycle pattern that can be lifted into any CLI or server needing resilient port ownership.
Regex-based component inventory builder that classifies production components as bespoke, wrapped, or vendored, and extracts prop contracts across React, Angular, Web Components, and Astro. The extensible detector pattern applies to codebase analysis beyond Figma.
Shared color and geometry comparison utilities such as figmaRGBAToHex, normalizeColor, and numericClose, used by diff and parity engines. Tiny, dependency-light helpers that solve cross-format numeric and color comparison in any design-tool pipeline.