Skip to main content
Glama
skulidropek

figma-tunnel-mcp

by skulidropek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to figma-tunnel-mcp

No user-submitted related servers found.

    Related Servers

    • Figma MCP Server

      hadi21k
      A
      license
      Not graded
      quality
      C
      maintenance
      Empowers AI assistants to control Figma via natural language, enabling creation and modification of designs, components, variables, and exports through a WebSocket bridge.
      1,589 npm
      2
      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

    • TalkToFigma

      Takeaki0817
      A
      license
      B
      quality
      C
      maintenance
      Enables local AI agents to generate and edit Figma designs via the Plugin API through a WebSocket relay, with no rate limits and all communication remaining local.
      50
      860 npm
      MIT

    • Talk to Figma MCP

      mhue26
      F
      license
      B
      quality
      F
      maintenance
      Enables AI agents to read and modify Figma designs programmatically through WebSocket communication, supporting document manipulation, styling, text replacement, and component management.
      42
      2
      -
    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.4/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is slight overlap between get_selection and read_my_design, and between set_selections and set_focus. Annotation and text tools are clearly separated by singular/plural variants.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case, e.g., create_frame, delete_node, set_fill_color. No mixed conventions or ambiguous verb choices.

    Tool Count3/5

    With 40 tools, the server is on the heavy side for a typical MCP server. While Figma is complex, the tool count may overwhelm agents; some property-setting tools could potentially be consolidated.

    Completeness4/5

    The tool set covers many common Figma operations (CRUD for nodes, components, styles, annotations, layout properties, and selection management). Missing operations like reordering or grouping nodes are minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources