About Layerbridge
Read, edit, and export the Figma file open in a local plugin. No REST API, no rate limits
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y layerbridgeFIGMA_BRIDGE_PORTLocal port the Figma plugin connects to; choose the same port in the plugin panelFIGMA_BRIDGE_OUTPUT_ROOTSExtra folders export tools may write to (; on Windows, : elsewhere). Default: working directory onlyFIGMA_ACCESS_TOKENSecretOptional Figma personal access token; enables REST tools (comments, versions, team files)FIGMA_BRIDGE_ALLOW_SCRIPTSAllow the run_script tool to execute Plugin API code in the open fileLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
116Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| pageId | string | No | Only this page (faster on big files) |
| fileKey | string | No | The fileKey of the Figma file. Required when several files are connected; see list_files. |
| includeVariants | boolean | No | Also list each variant inside a set (default false) |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.