Skip to main content
Glama
Halil-KAPLAN

Figma Bridge MCP

by Halil-KAPLAN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Figma Bridge 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
      49 npm
      1
      MIT

    • figma-bridge-mcp

      KaiUweHella
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server that lets AI assistants inspect, create, and update designs in Figma Desktop through a development plugin, requiring no Figma Personal Access Token or cloud services.
      12
      64 npm
      1
      MIT

    • Figma Agent MCP

      TrungLee003
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that connects AI clients to Figma via a WebSocket bridge and native plugin, enabling deterministic design operations like inspection, creation, mutation, styling, validation, and optimization.
      15 npm
      1
      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-meta-mcp

      shinjiyu
      A
      license
      A
      quality
      C
      maintenance
      Figma MCP server that lets agents execute arbitrary JavaScript inside a running Figma desktop app via a local development plugin, enabling real-time document inspection and manipulation while avoiding REST API rate limits.
      3
      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.2/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct action on a specific resource (e.g., create_frame vs. create_text, get_node vs. get_page). There is no obvious overlap or ambiguity between tools.

    Naming Consistency5/5

    All tools follow the consistent pattern of `figma_verb_noun` (e.g., figma_create_frame, figma_delete_node, figma_get_selection). No mixing of styles or irregular names.

    Tool Count5/5

    With 16 tools, the server covers a broad range of operations without being overwhelming. The count aligns well with the scope of a Figma bridge.

    Completeness4/5

    The tool surface covers creation, deletion, manipulation (move, resize, fill), reading (node, page, styles, variables), export, and advanced JS execution. Minor gaps like setting strokes or effects are present, but core workflows are well-supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources