Skip to main content
Glama
atezer

F-MCP (Figma MCP Bridge)

by atezer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to F-MCP (Figma MCP Bridge)

No user-submitted related servers found.

    Related Servers

    • figma-console-mcp

      Rydvansky
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access and manipulate Figma designs, including extracting design systems, creating and debugging UI components, and syncing design tokens bidirectionally.
      50,349 npm
      MIT

    • layerbridge

      muradyf
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to read, edit, check, and export the currently open Figma file locally, with support for design files, FigJam boards, and Slides decks plus quality checks and design-to-code workflows.
      MIT

    • MCP Figma

      YelowFlash09
      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.
      653 npm
      MIT

    • finish-line

      vypravec
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect Figma selections, navigate pages, render previews, generate starter code, and submit user-approved canvas edits through a local bridge.
      3 npm
      MIT

    • figma-mcp-poor

      whoistus
      A
      license
      Not graded
      quality
      C
      maintenance
      AI assistants can read and inspect Figma design context locally via a plugin, without external API keys or rate limits.
      10 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

    B3.2/5.0

    Scored across 63 tools

    Disambiguation2/5

    Several tool families are hard to distinguish: figma_validate_screen and figma_scan_ds_compliance largely overlap, and get_variables/get_token_browser/get_library_variables/search_assets all serve similar discovery purposes. The create_variable/batch_create_variables/setup_design_tokens trio also has fuzzy boundaries. Descriptions help, but an agent will frequently need to read very closely to avoid picking the wrong tool.

    Naming Consistency4/5

    All tools share the figma_ prefix and snake_case convention, and most follow a verb_noun structure such as figma_create_frame or figma_delete_variable. A few generic or noun-style names like figma_use, figma_execute, and figma_rest_api are minor deviations from that pattern.

    Tool Count2/5

    63 tools is far beyond the typical well-scoped 3-15 range and exceeds even the 25+ threshold. Many tools are granular variants of the same concern, especially in variables, component discovery, and DS compliance. The broad Figma domain explains some of the size, but the surface is still bloated for agent navigation.

    Completeness4/5

    The tool set covers a wide range of Figma workflows: variables, components, design-system validation, exports, console logs, and prototyping. Generic figma_execute and figma_rest_api fill most remaining gaps, so the few missing explicit operations like deleting a component or prototype connection are minor rather than blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources