Skip to main content
Glama
ChenLongbetterapp

FigmaExporterMcp

by ChenLongbetterapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to FigmaExporterMcp

No user-submitted related servers found.

    Related Servers

    • figma-local-bridge

      david-buck
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-only MCP bridge that connects an MCP client to an open Figma file via a Figma plugin, enabling direct document editing, inspection, export, and audit without using the Figma REST API.
      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

    • pholly-figma-mcp

      mubzie
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP bridge for live Figma documents, enabling design inspection, editing, asset export, component authoring, and variable management through a plugin and WebSocket server without consuming Figma REST API requests.
      1
      MIT

    • Local Figma MCP Bridge

      ikoba0911
      A
      license
      Not graded
      quality
      D
      maintenance
      Unofficial local MCP bridge for reading the currently open Figma file through a Figma plugin. Provides tools to inspect selection, file info, and export selected nodes as SVG/PNG.
      MIT

    • local-figma-connector

      raslanismail87
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients like Codex to inspect, create, update, and export Figma designs through a local desktop plugin and bridge.
      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 65 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some overlap (e.g., get_selection vs. read_my_design, clone_node vs. create_component_instance). The descriptions help differentiate, but an agent might still confuse a few.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., create_rectangle, set_fill_color). No mixed conventions or irregularities.

    Tool Count3/5

    65 tools is high, covering extensive Figma functionality. While the domain justifies many, the number exceeds typical MCP server scopes and may be overwhelming for an agent.

    Completeness5/5

    The tool set is remarkably complete, covering creation, manipulation, deletion, variables, styles, annotations, and batch operations. No obvious gaps in core Figma design workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources