Skip to main content
Glama
toro1221

figmad-mcp

by toro1221
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to figmad-mcp

No user-submitted related servers found.

    Related Servers

    • Figma MCP Server

      manojcx-max
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access Figma design context, generate code from frames, extract variables, components, and layout data, and create or modify Figma files directly from MCP clients.
      -

    • figma-mcp

      Anakintano
      F
      license
      B
      quality
      D
      maintenance
      Enables AI agents to read, inspect, and export Figma designs programmatically. Provides tools for listing components, styles, and exporting assets in various formats.
      5
      1
      -

    • figma-mcp

      ChimbuezeDavid
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI-driven UI/UX design and prototyping in Figma by letting agents generate AutoLayout screens, modify canvas elements, and wire interactive prototype flows through natural language.
      MIT

    • Fimake

      chavisnguyen
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read, create, edit, and organize Figma documents directly through a local plugin bridge, without needing a Figma AI subscription.
      1
      Apache 2.0
    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.7/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as create_frame, create_rectangle, and create_text for different element types, and get_file, get_node, and get_selection for different retrieval methods. However, some overlap exists between analyze_codebase and sync_design_tokens, as both involve code analysis and design tokens, which could cause mild confusion.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout, such as create_frame, delete_node, export_image, get_components, and update_node. There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count4/5

    With 20 tools, the count is slightly high but reasonable for a Figma MCP server covering design operations, code analysis, and webpage capture. It includes core CRUD actions and specialized functions without feeling excessively bloated, though it borders on the upper limit of typical scope.

    Completeness5/5

    The tool set provides comprehensive coverage for Figma design workflows, including creation (e.g., create_frame, create_text), retrieval (e.g., get_file, get_node), updates (update_node), deletion (delete_node), export (export_image), and integration with codebases and webpages. No obvious gaps are present, supporting full lifecycle operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources