Skip to main content
Glama
Echoxiawan

Figma MCP Tool

by Echoxiawan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Figma MCP Tool

No user-submitted related servers found.

    Related Servers

    • figma-mcp

      Anakintano
      F
      license
      B
      quality
      D
      maintenance
      Enables AI agents to read, inspect, and export Figma designs programmatically. Provides tools for listing components, styles, and exporting assets in various formats.
      5
      1
      -

    • Figma MCP

      alucardeht
      F
      license
      A
      quality
      D
      maintenance
      Enables interaction with Figma files through intelligent API access, providing navigation, asset extraction, and design token retrieval with 95% token-optimized compact tree output format.
      15
      1
      -

    • 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

    • figma-mcp-server

      DRX-1877
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables developers to extract and organize Figma design files, including complete node data (tree structure and images) for AI understanding and code generation.
      MIT

    • Figma MCP Server

      anishtejwanigemi-max
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Figma files through tools that list projects/files, fetch design data, and generate React+Vite frontend code directly from Figma frames.
      4
      1,772 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between 'export_multiple_images' and 'get_node_images' that could cause confusion. The descriptions help differentiate them, but the boundaries are not perfectly clear.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern with minor deviations, such as 'export_multiple_images' using an adjective. Overall, the pattern is readable and predictable across the tool set.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a Figma integration server. Each tool appears to serve a specific purpose related to extracting or retrieving design assets and data.

    Completeness4/5

    The tool set covers key operations for accessing Figma assets and styles, but there are minor gaps such as updating or modifying nodes. Agents can likely work around these limitations for most common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources