Skip to main content
Glama
drake-yuan

smart-figma-mcp

by drake-yuan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to smart-figma-mcp

No user-submitted related servers found.

    Related Servers

    • ds-mcp-sync

      blumaa
      F
      license
      A
      quality
      D
      maintenance
      Syncs design tokens and components from Figma to a Design System codebase, enabling automated generation of React components and Storybook stories.
      5
      -

    • Figma Context MCP

      cola-sk
      A
      license
      A
      quality
      D
      maintenance
      Converts Figma designs into structured code context with token-aware styling, enabling AI agents to generate production-level frontend code.
      1
      9 npm
      MIT

    • Pixelbyte Figma MCP Server

      Rylaa
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables seamless integration with Figma API for extracting design tokens, generating production-ready code in multiple frameworks, capturing screenshots, and managing design assets directly from Figma.
      5
      MIT

    • AllCrew Figma Workspace MCP

      mal4i6ka
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read the live state of an open Figma file — variables, modes, components, prototype edges and assets — and to export design tokens and code packages for web, iOS, Android, React, Django and Tauri through a user-run loopback bridge with separate read and write gates.
      2
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and descriptions clarify borderline cases (e.g. probe_astryx before fetch_astryx_contract, remember_mapping vs import_mappings). There is mild overlap around mapping persistence, but nothing severely ambiguous.

    Naming Consistency4/5

    Predominantly a consistent verb_noun snake_case pattern (save_component, fetch_figma_node, export_mappings, refresh_crl). Minor deviations come from prefixed domain names (compile_figma_component, fetch_astryx_contract) but the convention is readable and predictable.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range and each tool maps to a concrete step in the Figma-to-component workflow. No obvious padding.

    Completeness4/5

    Covers the core lifecycle: fetch node, compile, save component, scan library, and mapping management (remember/export/import/health). Minor gaps exist, such as no explicit update/delete for components or individual mapping entries, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources