Skip to main content
Glama

Related Servers

Alternatives to Figma MCP

No user-submitted related servers found.

    Related Servers

    • 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
      37 npm
      11
      MIT
    • 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
      2,347 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to extract, inspect, search, and bundle design context from local Figma .fig files entirely offline, exposing frame summaries, node context, style tokens, assets, vector SVGs, and visual-match review via MCP.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Unofficial local MCP bridge for reading the currently open Figma file through a Figma plugin. Provides tools to inspect selection, file info, and export selected nodes as SVG/PNG.
      MIT
    • 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
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to read Figma file hierarchies, node properties, and rendered images locally via MCP, using a personal access token without Figma's hosted MCP integration.
      -

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are fully distinct: list_frames discovers available frames while fetch_frame retrieves and writes a specific frame. There is no overlap or ambiguity in their responsibilities.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern and use consistent snake_case naming. The singular/plural distinction (fetch one frame vs. list many frames) aligns with their semantics.

    Tool Count3/5

    With only two tools, the server feels minimal and borderline thin. The pair supports a basic list-then-fetch workflow but leaves little room for broader Figma integration beyond frame extraction.

    Completeness3/5

    The server covers listing and fetching frames, but it only lists top-level frames, leaving nested-frame discovery as a notable gap. There are also no tools for other common Figma actions like retrieving comments or asset exports, making the surface feel incomplete for a general Figma MCP.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues