Skip to main content
Glama
AlexZai007

figma-unlimited-mcp

by AlexZai007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to figma-unlimited-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • figma-mcp-rust

      alvinindra
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI tools to read and write Figma designs via a plugin bridge, bypassing the Figma REST API and rate limits.
      52
      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
      -

    • figma-meta-mcp

      shinjiyu
      A
      license
      A
      quality
      C
      maintenance
      Figma MCP server that lets agents execute arbitrary JavaScript inside a running Figma desktop app via a local development plugin, enabling real-time document inspection and manipulation while avoiding REST API rate limits.
      3
      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

    A4.1/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource type, from creation tools like create_stickies and create_tables to query tools like list_nodes and find_nodes. The descriptions clearly separate similar operations, e.g., create_diagram vs. create_shapes + create_connectors, and update_nodes vs. arrange_nodes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (create_*, get_*, list_*, update_nodes, arrange_nodes, focus_view). No mixed conventions or vague verbs are present.

    Tool Count4/5

    At 19 tools, the set is slightly above the typical 3-15 well-scoped range, but the breadth is justified by the many content types FigJam supports (stickies, shapes, tables, code blocks, etc.). Each tool has a clear role, so the count feels reasonable rather than bloated.

    Completeness5/5

    The tool surface covers the full lifecycle for FigJam content: read (list_nodes, get_node, get_board_info, find_nodes), create (all create_* tools), update (update_nodes, arrange_nodes), delete, plus export and viewport focus. The create_demo_board tool even provides a ready-made showcase, indicating a thorough understanding of the domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources