Skip to main content
Glama
haju-xp

figma-free-mcp

by haju-xp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to figma-free-mcp

No user-submitted related servers found.

    Related Servers

    • Figma Console MCP Server

      Baskaran03528
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact directly with Figma Desktop for creating UI components, managing design tokens, and auditing files through natural language. It establishes a live connection between the AI and the Figma API via a local server and companion plugin.
      79,756 npm
      MIT

    • figma-mcp-server

      karthiks3000
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude AI to extract design information from Figma files and create or update designs via a Figma plugin, supporting both readonly and write modes.
      9
      36
      ISC

    • Layerwright

      shayan-m81
      A
      license
      A
      quality
      A
      maintenance
      Turn HTML and Claude Design exports into native, editable Figma frames with Auto Layout and your Design System components, build screens and prototypes from prompts, and implement Figma frames in code with your own React components. Runs locally with Figma desktop (no API keys or cloud): run npx layerwright init, import the plugin in Figma, see the Quickstart in the README.
      8
      22
      9
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 100 tools

    Disambiguation3/5

    Many tools target the same resource with fine-grained operations (e.g., multiple fill-setting tools, many text property setters, and get_node_info vs get_nodes_info). While descriptions clarify distinctions, the sheer number of tools increases risk of misselection, especially between set_image and set_image_fill, or among text manipulation tools.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., set_fill_color, create_rectangle, delete_node). A few outliers like boolean_operation and css_class_to_figma_style break the pattern, but these are rare. Overall naming is predictable and clear.

    Tool Count2/5

    100 tools is very heavy for an MCP server. While the scope (Figma design, FigJam, variables, CSS) is broad, many tools could be combined (e.g., all text property setters could be a single set_text_properties). This count overwhelms the agent and exceeds typical expectations for a coherent tool set.

    Completeness5/5

    The tool set covers the full lifecycle of Figma objects: create, read, update, delete for frames, pages, components, instances, styles, variables, and more. Also includes design system audit, CSS sync, and FigJam-specific tools. No obvious gaps for common design tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources