Skip to main content
Glama
angelostark

figma-drive

by angelostark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to figma-drive

No user-submitted related servers found.

    Related Servers

    • Figma Export MCP

      jornobam
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to analyze arbitrary Figma files, collaborate with users on export and naming rules, bulk-export images, and upload verified results to a single Yandex Disk account.
      12
      1 npm
      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 Tool

      Echoxiawan
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Figma designs through the Figma API, allowing users to export images in multiple formats, extract style data and CSS, analyze design elements, and retrieve SVG code from Figma files. Supports batch operations and comprehensive design element analysis including images, vectors, and components.
      7
      12 npm
      11
      MIT

    • Figma MCP

      scalably-io
      A
      license
      A
      quality
      A
      maintenance
      Enables listing top-level frames in a Figma file and fetching a selected frame's rendered PNG, node JSON, and image-fill map into a local output directory.
      2
      55 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.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools are mostly distinct: export_figma_frames only exports, upload_to_drive only uploads, and figma_to_drive combines both with parsing. There is slight overlap due to figma_to_drive covering the other two, but descriptions clarify the pipeline's additional functionality.

    Naming Consistency4/5

    Two tools follow verb_noun snake_case (export_figma_frames, upload_to_drive), but figma_to_drive breaks pattern by using a description phrase. Consistent otherwise.

    Tool Count4/5

    Three tools is on the lower side but appropriate for a focused figma-to-drive integration. Each tool serves a clear purpose, and the pipeline reduces redundancy.

    Completeness3/5

    Covers the core export-upload workflow, but lacks features like listing frames or managing Drive files. The pipeline assumes a specific naming convention, which may limit flexibility.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources