Figbridge vs Layerbridge
A side-by-side look at the Figbridge and Layerbridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figbridge for architecture & design work as a local process; choose Layerbridge for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Figbridge when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FIGBRIDGE_PORT.
Choose Layerbridge when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FIGMA_BRIDGE_PLAYWRIGHT. - You want tools like
check_accessibility, outputDir, lint_design_system.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 45/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | FIGBRIDGE_PORT | FIGMA_BRIDGE_PLAYWRIGHT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 13 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 11 |
| Full listing | View Figbridge | View Layerbridge |
Tools & capabilities
Figbridge tools
No tool names declared yet. Check the project README from the listing page.
Layerbridge tools 11
check_accessibilityoutputDirlint_design_systemfix_design_systemget_code_contextexport_tokensimport_tokenscompare_to_imageimport_urlFIGMA_BRIDGE_PLAYWRIGHTjpeg-js
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Figbridge
{
"mcpServers": {
"figbridge": {
"command": "npx",
"args": [
"-y",
"figbridge-mcp"
],
"env": {
"FIGBRIDGE_PORT": "YOUR_FIGBRIDGE_PORT_HERE"
}
}
}
}
Layerbridge
{
"mcpServers": {
"layerbridge": {
"command": "npx",
"args": [
"-y",
"layerbridge@latest"
],
"env": {
"FIGMA_BRIDGE_PLAYWRIGHT": "YOUR_FIGMA_BRIDGE_PLAYWRIGHT_HERE"
}
}
}
}
Frequently asked questions
Figbridge is categorized under Architecture & Design and uses a local stdio subprocess. Layerbridge belongs to Architecture & Design and uses a local stdio subprocess. Pick Figbridge for architecture & design work and Layerbridge for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Figbridge has no declared pricing — check the project's own site. Layerbridge has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add figbridge and layerbridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figbridge has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 13 GitHub stars. Layerbridge has 51/100 (Good) with 0 views, 0 installs and 1 GitHub stars.