Layerbridge MCP Server

What the code does

We read the source, 17 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      const status = await writeBytes(bytes, path.join(outputDir, file), overwrite);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add layerbridge -- npx -y layerbridge

{
  "mcpServers": {
    "layerbridge": {
      "args": [
        "-y",
        "layerbridge"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.layerbridge]
command = "npx"
args = ["-y", "layerbridge"]

{
  "mcpServers": {
    "layerbridge": {
      "args": [
        "-y",
        "layerbridge"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "layerbridge": {
      "args": [
        "-y",
        "layerbridge"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: FIGMA_BRIDGE_PORT (Local port the Figma plugin connects to; choose the same port in the plugin panel), FIGMA_BRIDGE_OUTPUT_ROOTS (Extra folders export tools may write to (; on Windows, : elsewhere). Default: working directory only), FIGMA_ACCESS_TOKEN (Optional Figma personal access token; enables REST tools (comments, versions, team files)), FIGMA_BRIDGE_ALLOW_SCRIPTS (Allow the run_script tool to execute Plugin API code in the open file). The author declared them in the registry entry; get the values from the project itself.