Skip to main content
Glama
kiettt8-product

figma-ui-mcp

by kiettt8-product
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to figma-ui-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • figma-local-bridge

      A1tolia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and modify the currently open Figma design file through a paired local Figma plugin, supporting operations like creating nodes, editing properties, and exporting PNG/SVG.
      162 npm
      1
      MIT

    • Figma Codex Bridge

      xiaobai59
      A
      license
      A
      quality
      B
      maintenance
      Enables Codex and other MCP clients to read design context from Figma Desktop via a local bridge, providing design tokens, component trees, and screenshots without an API token.
      7
      MIT

    • Writable Figma MCP Bridge

      chenyiwanshishen-source
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to read and modify the user's currently open Figma file by executing JavaScript in Figma's sandbox, all through a local bridge with status monitoring, node jumping, and automatic rollback on errors.
      1
      MIT

    • 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.
      2
      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

    A4.3/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: read, write, validate, docs, assets, status, plan. The only overlap is between figma_rules and design_system_context, both providing design rules but from different sources, which could cause minor confusion.

    Naming Consistency4/5

    The consistent 'figma_' and 'design_system_' prefixes create clear namespaces. However, the second part mixes nouns (status, docs, rules, assets, context) and verbs (read, write, validate, plan), preventing a fully uniform verb_noun pattern.

    Tool Count5/5

    10 tools is perfectly within the ideal range and each tool serves a distinct step in the design workflow—status check, planning, reading, writing, validation, and design-system management. No tool feels redundant or excessive.

    Completeness5/5

    The set covers the complete lifecycle: connectivity check, design context gathering, planning, code generation, asset import, and validation. There are no obvious missing operations for the intended purpose of generating Figma UI from a design system.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources