Skip to main content
Glama
AvYour

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Figxel

No user-submitted related servers found.

    Related Servers

    • figma-bridge-mcp

      KaiUweHella
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server that lets AI assistants inspect, create, and update designs in Figma Desktop through a development plugin, requiring no Figma Personal Access Token or cloud services.
      12
      16 npm
      1
      MIT
    • 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

    • localfig

      LucasGorgal
      A
      license
      A
      quality
      B
      maintenance
      The Figma desktop app as an MCP server. Gives AI agents the full Figma Plugin API on your open file: read, write, tokens, components, exports, undo. Runs locally with no cloud API, no token and no quota.
      10
      40 npm
      1
      MIT

    • figma-mcp-write-server

      oO
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides write access to Figma through the Plugin API, enabling AI agents to create, modify, and manage Figma designs programmatically.
      23
      -
    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.4/5.0

    Scored across 133 tools

    Disambiguation3/5

    Descriptions are exceptionally detailed and often explicitly point to the right sibling tool, but with 133 tools there are many closely related operations (e.g., figma_get_node vs figma_get_nodes_info, figma_set_text vs figma_set_text_range vs figma_set_text_properties, figma_move_nodes vs figma_reparent_nodes vs figma_reorder_nodes, and several export/check tools). An agent can usually disambiguate with effort, but the sheer number and overlapping boundaries will cause occasional misselection.

    Naming Consistency5/5

    Every tool uses the same predictable pattern: the `figma_` prefix followed by snake_case verb_noun (e.g., figma_create_variable, figma_get_design_context, figma_set_fills, figma_delete_nodes). There are no camelCase or mixed-style exceptions, making the set highly consistent and readable.

    Tool Count1/5

    133 tools is an extreme mismatch for an MCP tool surface, far beyond the typical 3–15 range and well past the 50+ threshold for a severe overload. Even accounting for the broad Figma Design/FigJam/Slides/motion domain, the count makes the set unwieldy for an agent to navigate.

    Completeness5/5

    The surface covers create, read, update, and delete for nodes, variables/tokens, styles, components, instances, prototypes, FigJam boards, Slides decks, and motion, plus export and review workflows. No obvious lifecycle gaps remain for the stated Figma automation purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources