Skip to main content
Glama
shaxaydev

Figma Local Bridge

by shaxaydev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Figma Local Bridge

No user-submitted related servers found.

    Related Servers

    • Figma Native MCP

      tomasmarekk
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that lets MCP clients inspect and edit the Figma document currently open in the Figma desktop app using a local bridge and development plugin.
      MIT

    • figma-bridge-mcp

      KaiUweHella
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server that lets AI assistants inspect, create, and update designs in Figma Desktop through a development plugin, requiring no Figma Personal Access Token or cloud services.
      12
      16 npm
      1
      MIT

    • localfig

      LucasGorgal
      A
      license
      A
      quality
      B
      maintenance
      The Figma desktop app as an MCP server. Gives AI agents the full Figma Plugin API on your open file: read, write, tokens, components, exports, undo. Runs locally with no cloud API, no token and no quota.
      10
      15 npm
      2
      MIT

    • Figxel

      AvYour
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server paired with a Figma desktop plugin that enables AI agents to read, build, edit, and animate real, editable designs in the Figma file you have open. It supports layers, components and variants, styles, variables and modes, prototypes, keyframes, video export, and self-checking of layouts, motion, and FigJam or Slides reads.
      140
      13 npm
      4
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct operation: connection status, document reading, font listing, node creation/update/deletion, export, viewport focus, prototype linking, and frame reparenting. The only borderline pair is update_nodes vs move_frames_to_page, but the latter is narrowly scoped to prototype eligibility and the description makes the boundary explicit.

    Naming Consistency4/5

    All tools share a consistent figma_ snake_case prefix, which makes the set predictable. A few entries are noun-only (figma_status, figma_document, figma_fonts) rather than verb_noun like the rest, a minor deviation.

    Tool Count5/5

    Ten tools is well-scoped for a local Figma bridge covering read, write, export, and prototyping operations. Each tool earns its place with no redundant entries.

    Completeness4/5

    The surface covers the core lifecycle: connect, inspect, create, update, delete, export, focus, and prototype-link nodes, with rollback semantics. Minor gaps remain, such as SVG/image export options and style/token or component enumeration beyond font listing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources