Skip to main content
Glama
figma-bridge-mcp

figma-bridge-mcp

Related Servers

Alternatives to figma-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to draw UI directly on a Figma Desktop canvas and read existing designs back as structured JSON, tokens, CSS, and screenshots, all over a localhost bridge without external API keys.
      109 npm
      2
      MIT
    • 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
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI assistants and scripts to safely create, edit, query, and organize Figma designs—including frames, text, components, variables, styles, prototyping, and motion—through a local bridge to an open Figma plugin. Supports bulk operations, design tokens, live change events, and optional REST API tasks.
      188
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read, create, edit, and organize Figma documents directly through a local plugin bridge, without needing a Figma AI subscription.
      3
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to read and edit the file currently open in Figma Desktop through a local development plugin, supporting node inspection, JSON/image exports, and arbitrary Plugin API scripts without REST API rate limits.
      7
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read and edit a live Figma file through a local plugin bridge, with no API token or rate limits. Provides 85 tools for inspecting design context, creating and modifying nodes, managing styles and variables, and exporting screenshots, tokens, and SVG.
      67 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    The read/write/status triad is clearly distinct and docs-loading is separated from execution. The main friction is between figma_docs (which includes a 'rules' section with design principles) and figma_rules (which generates a rule sheet from the current file); an agent could reasonably load the wrong one for design guidance.

    Naming Consistency4/5

    All tools share the uniform figma_ prefix with a single lowercase token, which is easy to scan. The convention mixes verbs (write, read) with nouns (status, docs, rules), so it's predictable in style but not a strict verb_noun pattern.

    Tool Count4/5

    Five tools is a tight, well-scoped set for a Figma plugin bridge and each tool clearly earns its place. However, figma_write is a mega-tool absorbing dozens of operations (tokens, prototyping, variants, layout), so the effective surface is much larger than the count suggests.

    Completeness4/5

    The surface covers connection check, reading (trees, colors, screenshots), writing (create/modify/delete/group, tokens, prototyping, variants), API docs, and design-system rule extraction. Minor gaps remain—no explicit asset export/download tool and no comments/annotations access—but core lifecycle coverage is solid.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues