MCP Tools DirectoryAbout this integration
Read, edit and export the Figma file open in a local plugin. No REST API, no rate limits.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.3.0
- Package
- layerbridge
- Last compatibility test
- Not independently tested
Connect your agent
layerbridgeCore plugin operations are documented as local and do not require a Figma API token; optional REST tools require one, and the loopback bridge uses a locally managed token. Documentation reviewed only; Figma, the package, and optional REST endpoints were not exercised.
Capabilities: Read, edit, check, and export an open Figma file, Inspect accessibility and design-system conformance, Import and export design tokens, images, code context, and layouts
Connected profiles
Additional details
io.github.muradyf/layerbridge
Source ↗ · Checked 2026-09-170.3.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17layerbridge
Source ↗ · Checked 2026-09-250.3.0
Source ↗ · Checked 2026-09-25The stdio Node server talks over a loopback WebSocket to a Figma plugin operating on the currently open file.
Source ↗ · Checked 2026-09-19The core local path needs no Figma API token, optional REST tools require FIGMA_ACCESS_TOKEN, and the loopback RPC has its own per-user token; this mixed local and optional mechanism does not map cleanly to the native taxonomy.
Source ↗ · Checked 2026-09-19Claude Code can register the stdio server with npx -y layerbridge@latest; a separately installed Figma plugin and open plugin window are required.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19