Skip to main content
Glama
Gawasna

figma-antigravity-mcp

by Gawasna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to figma-antigravity-mcp

No user-submitted related servers found.

    Related Servers

    • figma-ui-mcp

      kiettt8-product
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.
      10
      222 npm
      MIT

    • figma-local-bridge

      A1tolia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and modify the currently open Figma design file through a paired local Figma plugin, supporting operations like creating nodes, editing properties, and exporting PNG/SVG.
      1
      MIT

    • TalkToFigma

      ManuelXI
      A
      license
      B
      quality
      C
      maintenance
      Enables writing to Figma from MCP clients like Claude Code without a Figma Dev seat, using a local WebSocket relay and a Figma dev plugin.
      44
      860 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

    • figsnap-mcp

      arimunandar
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to interact with the currently open Figma file via local MCP tools, including reading the design, extracting nodes as PNG, React, HTML or CSS, editing the canvas when permitted, and sharing saved component sets.
      39
      40 npm
      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

    A3.8/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target clearly distinct actions—auth, context detection, reading, exporting, uploading, writing, and file/diagram creation—and the descriptions actively steer between get_metadata and get_design_context. However, get_screenshot and download_assets both render node exports, and figma_auth_status/whoami both surface user identity, creating mild ambiguity.

    Naming Consistency4/5

    The majority of tools follow a clear verb_noun snake_case pattern like get_metadata, upload_assets, and create_new_file, with the figma_ auth/context cluster staying internally consistent. The bare whoami and the generic use_figma break the pattern slightly, but the overall convention remains predictable.

    Tool Count4/5

    13 tools is within the healthy range for a Figma integration, covering auth, current-context, inspection, assets, writing, file creation, and diagrams. It is slightly heavier than necessary because get_screenshot overlaps with the export side of download_assets and whoami partially duplicates figma_auth_status.

    Completeness5/5

    The set covers the full design-to-code lifecycle: authentication, detecting the active file, reading metadata and variables, extracting screenshots/assets, uploading assets, and mutating designs via use_figma. Creating new files and generating diagrams round out the surface with no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources