Skip to main content
Glama
mahmudcoding

Custom Figma MCP

by mahmudcoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Custom Figma MCP

No user-submitted related servers found.

    Related Servers

    • Fimake

      chavisnguyen
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read, create, edit, and organize Figma documents directly through a local plugin bridge, without needing a Figma AI subscription.
      Apache 2.0

    • finish-line

      vypravec
      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

    • 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
      MIT

    • Writable Figma MCP Bridge

      chenyiwanshishen-source
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to read and modify the user's currently open Figma file by executing JavaScript in Figma's sandbox, all through a local bridge with status monitoring, node jumping, and automatic rollback on errors.
      1
      MIT

    • figma-agent-mcp

      ChinaCarlos
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI agents to Figma through a local WebSocket bridge, enabling read/write access to open Figma files, node manipulation, and AI-assisted rename/group features.
      4
      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.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 issues

    Resources