Skip to main content
Glama
xlzuvekas

Figma Copilot

by xlzuvekas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Figma Copilot

No user-submitted related servers found.

    Related Servers

    • MCP Figma

      YelowFlash09
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read and modify Figma designs programmatically, supporting design analysis, element creation, text replacement, annotations, auto-layout configuration, and prototype visualization through natural language commands.
      461 npm
      MIT

    • Figma MCP Server

      AIYA861202
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Cursor to interact with Figma designs programmatically. Supports reading design information, modifying elements, creating components, managing text content, and automating design workflows through natural language commands.
      860 npm
      MIT

    • figma-console-mcp

      Rydvansky
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access and manipulate Figma designs, including extracting design systems, creating and debugging UI components, and syncing design tokens bidirectionally.
      27,155 npm
      MIT

    • F-MCP (Figma MCP Bridge)

      atezer
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to read, analyze, and modify Figma designs, manage design tokens, and create prototype connections, all while keeping data local.
      63
      69 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

    B3/5.0

    Scored across 75 tools

    Disambiguation2/5

    Many tools overlap in purpose, especially the deprecated aliases (get_selection, get_node_info, get_nodes_info, scan_text_nodes) that duplicate current equivalents. Text-editing options are also numerous and subtly different (set_text_content, update_text_preserving_formatting, smart_text_replace), which makes misselection likely.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern (get_, create_, set_, update_, delete_), but there are minor inconsistencies like read_my_design vs get_document_info and deprecated variants with different names (get_nodes_info vs get_multiple_nodes_info).

    Tool Count1/5

    75 tools is far beyond what an agent can effectively consider, and many are deprecated duplicates or near-overlapping variants. Even for a broad Figma surface, the set should be consolidated to reduce cognitive load and redundant alternatives.

    Completeness4/5

    The surface covers design nodes, text styling, layout, components, slides, annotations, and connections, so most core workflows are represented. However, some gaps exist, such as renaming or deleting components/styles and managing frames/pages more broadly, though these are workable around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources