Skip to main content
Glama
shinjiyu

figma-meta-mcp

by shinjiyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to figma-meta-mcp

No user-submitted related servers found.

    Related Servers

    • Figma Native MCP

      tomasmarekk
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that lets MCP clients inspect and edit the Figma document currently open in the Figma desktop app using a local bridge and development plugin.
      MIT

    • claude-talk-to-figma-mcp

      litoondev
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to read, analyze, and modify Figma designs, including comment management via Figma's REST API. Works with any Figma account and supports parallel execution.
      238 npm
      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-mcp-write-server

      oO
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides write access to Figma through the Plugin API, enabling AI agents to create, modify, and manage Figma designs programmatically.
      23
      -
    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

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools serve clearly distinct functions: health check, arbitrary code execution, and selection introspection. There is no overlap in purpose, even though figma_selection_info could be replicated via figma_exec; it is presented as a convenience wrapper with a distinct scope.

    Naming Consistency4/5

    All tool names share the figma_ prefix, but the second part is not uniformly verb_noun. figma_health and figma_selection_info are noun phrases, while figma_exec is a verb. This is a minor inconsistency, but the pattern is still predictable and readable.

    Tool Count4/5

    Three tools is a small but reasonable set for a bridge server. The health and selection tools handle occasional meta needs, while figma_exec provides the core general-purpose capability. It is slightly on the lean side, but not insufficient.

    Completeness5/5

    figma_exec offers arbitrary access to the Figma Plugin API, making the tool surface effectively complete for any operation. The other two tools cover operational status and a common convenience need. There are no obvious dead ends or missing core workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources