Skip to main content
Glama
stuffbucket

figmma

by stuffbucket
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to figmma

No user-submitted related servers found.

    Related Servers

    • figma-developer-mcp

      p1t42
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Figma files, nodes, styles, and image assets via the Figma REST API for any MCP client, using your own personal access token.
      -

    • figma-local-bridge

      A1tolia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and modify the currently open Figma design file through a paired local Figma plugin, supporting operations like creating nodes, editing properties, and exporting PNG/SVG.
      162 npm
      1
      MIT

    • 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.
      -

    • 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.
      -

    • Figma Edit MCP

      neozhehan
      A
      license
      A
      quality
      A
      maintenance
      Read, create, and modify Figma designs programmatically via MCP, empowering AI to execute Figma changes safer, cleaner, and faster.
      45
      65 npm
      9
      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

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are distinct: get_current_user, parse_figma_url, get_file_info, and get_file_comments have clear separate purposes. However, list_project_files and search_projects both retrieve files and could cause confusion, especially since search_projects is misnamed (it searches files, not projects). The overlap is manageable with careful descriptions.

    Naming Consistency4/5

    The naming pattern is mostly consistent with verb_noun (e.g., get_current_user, list_team_projects, get_file_comments). The exception is search_projects, which uses a verb but the noun does not match its actual function (searching files, not projects). This deviation slightly undermines predictability.

    Tool Count5/5

    With 7 tools, the server is well-scoped. It covers auth, URL handling, navigation, metadata retrieval, and comments without being overwhelming. Each tool serves a clear purpose and the count is within the ideal 3-15 range for a focused integration.

    Completeness2/5

    The tool surface is heavily read-only and misses core Figma operations. There is no way to fetch actual design content (nodes, layers, styles) or export images, which are essential for a design tool. Additionally, there are no create, update, or delete operations, leaving the server limited to metadata and comment retrieval.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources