Skip to main content
Glama
Figma Console MCP Server

Figma Console MCP Server

by GreyCatVP

Related Servers

Alternatives to Figma Console MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to access and manipulate Figma designs, including extracting design systems, creating and debugging UI components, and syncing design tokens bidirectionally.
      16,945 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to read, create, and modify Figma designs, synchronize design tokens bidirectionally, and auto-document component-variant sets via Obra Autodocs integration.
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read and modify Figma designs programmatically, supporting design analysis, element creation, text replacement, annotations, auto-layout configuration, and prototype visualization through natural language commands.
      1,908 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to read, analyze, and modify Figma designs, manage design tokens, and create prototype connections, all while keeping data local.
      63
      15 npm
      10
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Figma designs programmatically, supporting comprehensive design automation including text manipulation with formatting preservation, batch operations, prototyping, auto-layout configuration, and component management.
      75
      19 npm
      5
      MIT

    TDQS

    B3.4/5.0

    Scored across 130 tools

    Disambiguation2/5

    The surface contains many near-duplicate tools whose boundaries require reading long descriptions to resolve: figma_take_screenshot vs figma_capture_screenshot vs figma_get_component_image, figma_get_file_data vs figma_get_file_for_plugin vs figma_get_file_at_version, figma_get_variables vs figma_get_token_values vs figma_get_design_system_kit, and figma_diff_versions vs figma_get_changes_since_version vs figma_get_design_changes. Many descriptions even contain explicit 'NOT this, use that instead' disclaimers, which is a strong signal of inherent overlap rather than distinct purposes.

    Naming Consistency4/5

    Nearly everything follows the prefixed snake_case verb_noun pattern (figma_get_*, figma_create_*, figma_set_*, figjam_create_*), with domain prefixes figma_/figjam_ used coherently. Minor deviations exist (figma_execute, figma_diagnose, figma_ds_analyze, figma_manage_animation_styles, figma_lint_design), but they remain readable and predictable.

    Tool Count1/5

    130 tools in a single server is far beyond a manageable set for an agent to select from, spanning unrelated domains (Slides, FigJam, variables/tokens, motion, shaders, version history, code accessibility, design-system extraction). This is effectively six or seven servers bundled into one and will cause context bloat and misselection regardless of individual tool quality.

    Completeness4/5

    Coverage of the Figma domain is genuinely broad: variables and modes have full CRUD plus batch and token import/export, slides have create/delete/duplicate/reorder/content, FigJam has create/read/arrange, comments have get/post/delete, and version history has list/diff/blame/changelog. Remaining gaps are minor, such as no comment update/edit tool and no style creation or deletion counterpart to figma_get_styles.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues