Skip to main content
Glama
LeoGCode

figma-reader-mcp

by LeoGCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to figma-reader-mcp

No user-submitted related servers found.

    Related Servers

    • figme

      ntson9p
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to read and inspect local Figma .fig files entirely offline, exposing document structure, geometry, styles, text, components, variables, and embedded images via MCP tools.
      12
      628 npm
      MIT

    • ai-sdlc-figma-mcp-server

      vjackk
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that wraps the Figma REST API, providing tools like get file metadata, list frames, and export node image URLs for AI SDLC agents.
      -

    • figctx-mcp

      POLAX7
      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
    • Figma MCP Server by figma

      Figma MCP Serverofficial

      figma
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides Figma design context to AI agents, enabling code generation, design system integration, and canvas manipulation through MCP.
      2,014
      -

    • Figma MCP Server

      manojcx-max
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access Figma design context, generate code from frames, extract variables, components, and layout data, and create or modify Figma files directly from MCP clients.
      -
    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

    A4.2/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: auth, file listing/loading, tree/node access, search, text extraction, variables/styles/components, token usage, screenshot, and image export. Where tools seem adjacent (search vs. get_text, get_tree vs. get_node), the descriptions make the boundary explicit.

    Naming Consistency5/5

    All tools share the figma_ prefix and follow a consistent verb_noun pattern: list_files, load_file, get_tree, get_node, get_text, get_variables, get_styles, get_components, export_image_fills. Even the less noun-like names like figma_status and figma_login fit the predictable style.

    Tool Count5/5

    14 tools is well within the ideal range for a reader-focused server. Each tool covers a meaningful slice of Figma reading/export functionality without redundancy or bloat.

    Completeness5/5

    The surface covers the full read lifecycle: file discovery and loading, structural traversal, node-level design details, text and search, design tokens/styles/components, usage analysis, rendering, and bitmap asset export. For a "reader" server, there are no obvious dead ends or missing operations.

    Resources