Skip to main content
Glama
Sangwonee

Figma MCP Connect

by Sangwonee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Figma MCP Connect

No user-submitted related servers found.

    Related Servers

    • TalkToFigma

      ManuelXI
      A
      license
      B
      quality
      C
      maintenance
      Enables writing to Figma from MCP clients like Claude Code without a Figma Dev seat, using a local WebSocket relay and a Figma dev plugin.
      44
      860 npm
      MIT

    • figma-local-bridge

      A1tolia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and modify the currently open Figma design file through a paired local Figma plugin, supporting operations like creating nodes, editing properties, and exporting PNG/SVG.
      1
      MIT

    • MC Figma Bridge

      mochammad123
      F
      license
      B
      quality
      C
      maintenance
      Enables Cursor (MCP client) to interact with an active Figma document through a local WebSocket bridge and Figma plugin, providing tools to read and modify canvas elements like text and frames.
      6
      -

    • pholly-figma-mcp

      mubzie
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP bridge for live Figma documents, enabling design inspection, editing, asset export, component authoring, and variable management through a plugin and WebSocket server without consuming Figma REST API requests.
      1
      MIT

    • local-figma-connector

      raslanismail87
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients like Codex to inspect, create, update, and export Figma designs through a local desktop plugin and bridge.
      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.9/5.0

    Scored across 44 tools

    Disambiguation2/5

    Several tools have overlapping purposes, such as get_selection vs read_my_design, set_text_content vs set_multiple_text_contents, and delete_node vs delete_multiple_nodes. Even where descriptions differ slightly, an agent could easily select the wrong tool for a common task.

    Naming Consistency4/5

    The vast majority of tools follow a consistent snake_case verb_noun pattern like create_rectangle, set_fill_color, and delete_node. A few exceptions like read_my_design and set_multiple_text_contents break the pattern, but the overall convention is clear.

    Tool Count2/5

    44 tools is a heavy surface for a single MCP server. Many tools are near-duplicates or batch variants that could be consolidated, making the set feel bloated rather than carefully scoped.

    Completeness3/5

    The server covers a broad range of Figma operations including node CRUD, layout, styles, components, annotations, export, and prototyping reactions. However, there are notable gaps such as grouping, layer ordering, text style manipulation, and more advanced vector/constraint operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources