Layerbridge

io.github.muradyfPublished by GitHub account muradyfv0.3.0Updated Oct 24, 2026

Read, edit and export the Figma file open in a local plugin. No REST API, no rate limits.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Lets an assistant read, edit and export the Figma file currently open in a local Figma plugin, without using the Figma REST API.

What you can do
Layerbridge connects an assistant to the Figma file open in a local plugin, so it can read and edit that file and export content from it. It works through the plugin rather than the Figma REST API, which the description says avoids rate limits. An optional Figma personal access token enables additional REST-based tools such as comments, versions and team files. A run_script tool can execute Plugin API code in the open file when explicitly enabled.
When to use it
Useful when you want an assistant to inspect or modify the Figma document you currently have open, or to export assets from it, without hitting REST API rate limits. It suits local, desktop-based design workflows where the plugin is running alongside the assistant.
Requirements
Runs as a local process on the user's machine, installed from the npm package layerbridge over stdio, and is desktop only. It needs the Figma plugin running and connected on a local port (FIGMA_BRIDGE_PORT, which must match the plugin panel). FIGMA_ACCESS_TOKEN is optional and only needed for the REST tools. Export tools write to the working directory by default; FIGMA_BRIDGE_OUTPUT_ROOTS can add folders.
Before you install
FIGMA_ACCESS_TOKEN is a secret credential and should be handled as such. FIGMA_BRIDGE_ALLOW_SCRIPTS enables run_script, which executes Plugin API code in the open file; leave it off unless you intend that. Export tools write files, and FIGMA_BRIDGE_OUTPUT_ROOTS widens the folders they may write to, so keep it narrow. Edits made through the bridge change the open Figma document.

Installation

In SourceWeft

  1. Open Layerbridge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts