Skip to main content
Glama
sso-ss

figma-unified-mcp

by sso-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to figma-unified-mcp

No user-submitted related servers found.

    Related Servers

    • Figma Forge

      Liljimbo
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that bridges Claude Code to Figma, enabling AI-driven design creation, modification, and export via semantic tools and WebSocket communication.
      -

    • tokensStudioMCP

      Blyawon
      A
      license
      A
      quality
      D
      maintenance
      MCP server that reads Tokens Studio design tokens from Figma and makes them available to Claude Code, enabling token-aware code generation.
      38
      4
      MIT

    • figma-comments-mcp

      ejun-9
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets Claude read Figma file comments directly, with tools to list comment threads scoped to a frame or file and render images of pinned nodes.
      16 npm
      ISC
    • desrid-html-to-figma by Desrid

      desrid-html-to-figmaofficial

      Desrid
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server lets AI agents connect to Figma to read, analyze, create, and modify designs, including elements, styles, assets, and code generation. It works with free Figma accounts and supports parallel multi-agent use across MCP-compatible clients.
      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

    C2.6/5.0

    Scored across 106 tools

    Disambiguation2/5

    Multiple tools have overlapping responsibilities, especially around exporting: figma_export_png, figma_export_svg, figma_export_to_file, figma_get_images, and figma_screenshot all serve similar purposes. Retrieval also overlaps between figma_get_file, figma_get_node, figma_get_nodes, figma_search, and figma_scan_nodes_by_types, making misselection likely without reading descriptions carefully.

    Naming Consistency4/5

    The vast majority of tools follow the figma_verb_noun snake_case pattern, with predictable verbs like get, create, set, and delete. A few names break the pattern—figma_status, figma_cache, figma_boolean_operation, and figma_codegen_bundle—but these are exceptions rather than systemic inconsistencies.

    Tool Count1/5

    106 tools is an extreme count, far exceeding what an agent can efficiently evaluate in context. Even for a 'unified' Figma server, this surface area is unwieldy and would be better split into focused sub-servers; the tool prompt alone would consume enormous context.

    Completeness4/5

    Coverage is genuinely extensive: node CRUD, variables, styles, components, interactions, comments, exports, accessibility, codegen, and dev resources are all represented. Minor lifecycle gaps exist—such as updating or deleting comments and managing files/projects—but core design and development workflows do not hit dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources