Skip to main content
Glama
Custom Figma MCP

Custom Figma MCP

by mahmudcoding

Related Servers

Alternatives to Custom Figma MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read, create, edit, and organize Figma documents directly through a local plugin bridge, without needing a Figma AI subscription.
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect Figma selections, navigate pages, render previews, generate starter code, and submit user-approved canvas edits through a local bridge.
      3 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to read and edit the file currently open in Figma Desktop through a local development plugin, supporting node inspection, JSON/image exports, and arbitrary Plugin API scripts without REST API rate limits.
      7
      11 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to read designs, variables, selections, and node screenshots or exports from the currently open Figma file through a local desktop-plugin bridge, without consuming the official Figma MCP quota.
      9
      25 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to draw and modify designs directly on the Figma Desktop canvas via JavaScript and read existing designs back as structured data, CSS, component maps, and screenshots. It runs locally over a bridge without requiring a Figma API key.
      5
      599 npm
      MIT

    TDQS

    C2.8/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target distinct operations, but `figma.create_node` overlaps with specific create tools, and `figma.set_property` overlaps with `figma.update_node`. Descriptions help clarify, but some ambiguity remains.

    Naming Consistency5/5

    All tools follow a consistent `figma.verb_noun` pattern (e.g., `create_frame`, `get_node`), with no mixing of conventions.

    Tool Count4/5

    29 tools cover a broad range of Figma operations, but some tools could be merged (e.g., `call_api` and `rest_request`). Still, it's reasonably scoped for a comprehensive MCP server.

    Completeness3/5

    Covers node CRUD, styles/variables listing, events, and API access, but missing create for styles/variables and page management. Notable gaps for a full design tool surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues