figma-bridge
Related Servers
Alternatives to figma-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables local MCP-capable assistants to connect to Figma Desktop to read documents, pages, and selections, edit native layers and components, and export PNG/SVG across multiple files without Figma API keys.2MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to read and edit the file currently open in Figma Desktop through a local development plugin, supporting node inspection, JSON/image exports, and arbitrary Plugin API scripts without REST API rate limits.711 npmMIT
- AlicenseAqualityDmaintenanceEnables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read and modify the currently open Figma design file through a paired local Figma plugin, supporting operations like creating nodes, editing properties, and exporting PNG/SVG.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible AI clients to read and modify the user's currently open Figma file by executing JavaScript in Figma's sandbox, all through a local bridge with status monitoring, node jumping, and automatic rollback on errors.3MIT
- AlicenseNot gradedqualityBmaintenanceConnects an MCP client such as Claude Code to the Figma file open in the desktop app, letting the agent create frames, write text, apply styles, import images and SVGs, take screenshots, and run arbitrary Figma Plugin API code. Commands travel through a local development plugin instead of Figma's web API, so there are no tokens, quotas, or rate limits.50 npm3MIT
TDQS
Scored across 23 tools
The create_*/set_*/update_* families each target a distinct node property, and the read tools are mostly separable. There is mild overlap between figma_status, figma_get_document_info and figma_get_current_page (all report file/page context), and between figma_read_for_implement and figma_export_node (both dump node assets), but the descriptions clarify the boundaries.
Every tool uses a predictable figma_<verb>_<noun> snake_case pattern (get_node, create_frame, set_fill, delete_node). The only deviation is figma_status, which omits the verb, but it remains readable and clearly scoped as a status probe.
23 tools is on the heavy edge for a single-plugin bridge and could be consolidated (e.g. one generic style setter, or merging the three document/page reads). Most tools do earn a place as distinct Figma node primitives, so it is borderline rather than bloated.
The surface covers the full node lifecycle: read/inspect, create primitives, update geometry, style (fill, stroke, effects, radius, text style, auto layout), move/reparent, export and delete. Gaps remain around editing existing text content, grouping/boolean ops, and component/instance creation, but agents can work around these by recreating nodes.