Skip to main content
Glama
MaxsBond

Figma Bridge MCP

by MaxsBond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Figma Bridge MCP

No user-submitted related servers found.

    Related Servers

    • FreeMCP for Figma

      w4ndaja
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to read and write a user's Figma file through the Figma Plugin API, offline and privately, without API tokens or rate limits.
      13 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

    • 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

    • 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

    • figma-mcp

      BuiHung1612
      A
      license
      Not graded
      quality
      A
      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.
      184 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

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools are mostly distinct: status/list_pages/get_tree/run_script each serve a clear purpose. The only mild overlap is between get_tree (lightweight outline) and export_json (full export), but the descriptions clearly differentiate lightweight ID-hunting from full serialization, and export_image vs export_image_fills cleanly separate rendering from extracting source bytes.

    Naming Consistency4/5

    Consistent figma_ prefix with snake_case verb_noun pattern across nearly all tools (figma_list_pages, figma_get_tree, figma_export_json, figma_export_image, figma_run_script). The only deviation is figma_status, which omits a verb but remains readable and conventional for a health-check tool.

    Tool Count5/5

    Seven tools is well-scoped for a Figma plugin bridge: connection check, page listing, node discovery, and three export variants plus a scripting escape hatch. No redundancy and nothing feels thin.

    Completeness4/5

    Read/inspection coverage is comprehensive (status, pages, tree, JSON, image render, image fills). Modification is covered only indirectly through figma_run_script rather than dedicated create/update/delete tools, which is workable but a minor ergonomic gap for structured mutations.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources