Skip to main content
Glama
Sign In
Figma MCP Bridge

Figma MCP Bridge

by SrgGrch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Figma MCP Bridge

No user-submitted related servers found.

    Related Servers

    • figma-ui-mcp

      kiettt8-product
      A
      license
      A
      quality
      D
      maintenance
      Enables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.
      10
      697 npm
      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.
      527 npm
      2
      MIT

    • 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

    • codex-local-bridge

      mengkong30
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local MCP-capable assistants to connect to Figma Desktop to read documents, pages, and selections, edit native layers and components, and export PNG/SVG across multiple files without Figma API keys.
      2
      MIT

    • figma-local-bridge

      david-buck
      A
      license
      Not graded
      quality
      B
      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.
      527 npm
      3
      MIT

    • Figma Codex Bridge

      xiaobai59
      A
      license
      A
      quality
      C
      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
    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/5.0

    Scored across 10 tools

    Disambiguation4/5

    The read tools are mostly separable by scope: get_tree returns structure, find_nodes searches a bounded region, get_nodes fetches properties by nodeId, and get_context reports bridge state. The main soft spot is the tree/nodes/find_nodes cluster plus get_operation vs get_context, which an agent could plausibly swap, but the descriptions do enough to steer selection.

    Naming Consistency4/5

    All ten tools share a `figma_` prefix with a verb_noun pattern (get_tree, find_nodes, apply_batch, cancel_operation, export_node). The only deviation is `figma_navigate`, which drops the object noun, but the convention remains predictable overall.

    Tool Count5/5

    Ten tools is a well-scoped surface for a Figma bridge: reads, search, navigation, batched mutation, operation lifecycle, and export. Each tool maps to a distinct capability without padding.

    Completeness4/5

    The surface covers discovery, reading, mutation via apply_batch with preconditions, operation polling/cancel, and PNG/SVG export, so core workflows are closed. Minor gaps: no rollback/undo for applied batches (cancel explicitly does not revert), no file/document switching, and export limited to two formats.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources