Skip to main content
Glama
zaferdace

figma-spec-mcp

by zaferdace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to figma-spec-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      6 npm
      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

    • 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

    • Sunnyside Figma MCP

      tercumantanumut
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Figma designs to AI agents, enabling extraction of production-ready code, assets, and design tokens through natural language descriptions. Supports React, Vue, CSS, and Tailwind with real-time design system analysis.
      91,027 npm
      40
      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

    A3.8/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the Figma-to-code workflow (accessibility auditing, layout inspection, token extraction, flow extraction, component resolution, framework-specific mapping, etc.). Even the five map_to_* tools are clearly separated by target framework, and the extraction tools each focus on a different data type (tokens, flows, variants, states).

    Naming Consistency4/5

    Names follow a consistent snake_case convention and most use a verb_noun structure (audit_accessibility, extract_variants, resolve_components). A few conversion tools use a 'to' pattern (map_to_react, bridge_to_codebase) which is coherent, but flow_to_test_cases deviates by starting with a noun instead of a verb.

    Tool Count4/5

    With 19 tools, the count is on the heavier side but well-justified for a comprehensive Figma design-to-development server. Each tool serves a distinct purpose in the workflow, and the scope is broad enough to warrant the number without feeling bloated.

    Completeness5/5

    The tool surface covers the full read-only design-to-code pipeline: extraction, analysis, mapping to multiple frameworks, asset export, version diffing, component resolution, test case generation, and handoff readiness checks. There are no obvious missing operations for its stated purpose, and the addition of bridge_to_codebase and simplify_context further fills collaboration and context-efficiency gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources