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

    • 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
      47 npm
      2
      MIT

    • Figma Local Bridge

      shaxaydev
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that reads and edits a Figma Design file through a development plugin, creating real editable layers (frames, text, shapes, components, images) rather than flattened screenshots. It runs entirely on loopback with no personal access token, API key, or cloud bridge, letting an agent inspect documents, build and update layers, export previews, and wire up prototype navigation.
      10
      3 npm
      MIT

    • 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

    • Figma Local Bridge

      Miart
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP client to drive the real Figma Desktop plugin API through one local daemon, so agents can read and edit the open file, take screenshots, export assets, and inspect variables, components, and styles. Everything stays on 127.0.0.1 with no cloud, API keys, or Dev/Full seat required.
      3 npm
      1
      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

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources