Skip to main content
Glama
ManuelXI

TalkToFigma

by ManuelXI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to TalkToFigma

No user-submitted related servers found.

    Related Servers

    • Figma Bridge

      Clovis500c
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects an MCP client such as Claude Code to the Figma file open in the desktop app, letting the agent create frames, write text, apply styles, import images and SVGs, take screenshots, and run arbitrary Figma Plugin API code. Commands travel through a local development plugin instead of Figma's web API, so there are no tokens, quotas, or rate limits.
      42 npm
      3
      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

    • MC Figma Bridge

      mochammad123
      A
      license
      B
      quality
      D
      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
      ISC

    • OneWright

      heyxiaoze
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read and write Figma designs through a local WebSocket relay, turning Figma selections into framework-aware code and building/editing designs directly on the canvas. Provides 112 MCP tools for bidirectional design-code workflows with support for any MCP client.
      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

    B3.1/5.0

    Scored across 44 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes. The main confusion is between get_selection and read_my_design, which both describe retrieving current selection information, and scan_text_nodes could overlap somewhat with scan_nodes_by_types.

    Naming Consistency4/5

    The naming mostly follows a predictable verb_noun snake_case pattern (create_, get_, set_, scan_). Minor inconsistencies like read_my_design instead of get_selection_detailed and the out-of-place join_channel prevent a perfect score.

    Tool Count2/5

    44 tools is far beyond the typical well-scoped surface for a server, making it feel heavy and harder for agents to navigate. Many tools are batch variants (e.g., set_text_content vs. set_multiple_text_contents) that add surface area without adding much conceptual value.

    Completeness4/5

    The tool surface covers the core design workflow well: node manipulation, selection, layout, components, annotations, and image handling. Minor gaps exist, such as no tools for creating or editing styles and limited shape creation (only rectangle, frame, and text).

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources