Figma Local MCP
Related Servers
Alternatives to Figma Local MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to read, create, edit, and organize Figma documents directly through a local plugin bridge, without needing a Figma AI subscription.2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables a locally run agent or script to read and write a real Figma layer tree through a local bridge — inspecting node structure and variables, exporting screenshots into the model's context, and performing batched create/update/move/rename/delete operations that collapse into a single undo step. All traffic stays on localhost between the bridge and the Figma plugin, with design-token auditing, binding, and creation included.2 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect Figma selections, navigate pages, render previews, generate starter code, and submit user-approved canvas edits through a local bridge.3 npmMIT
- 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.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to read and write a user's Figma file through the Figma Plugin API, offline and privately, without API tokens or rate limits.40 npmMIT
- FlicenseAqualityDmaintenanceEnables AI agents to interact with Figma to create, read, and manage designs using the Figma REST API and a dedicated plugin. It supports advanced features like UI generation from text, webpage reconstruction in Figma, and design token synchronization with codebases.20-
TDQS
Scored across 21 tools
Most tools have clearly distinct purposes, but a few pairs could be confused: set_image_fill vs set_image_fill_from_path differ only by input source, and create_style_guide vs get_design_system touch overlapping design system concepts. The descriptions do help disambiguate these cases, so overall ambiguity is low.
All tool names consistently follow a verb_noun pattern (delete_node, create_style_guide, get_document, set_selection, etc.) with no mixing of camelCase or other conventions. This is highly predictable.
21 tools is borderline heavy for a local Figma plugin MCP server, but the domain (nodes, pages, styles, variables, images, connection, search) justifies a broad surface. Still, some adjacent tools could potentially be consolidated, making it slightly over-scoped.
The surface covers creation, reading, updating, deletion, selection, reordering, reparenting, export, image fills, pages, styles, variables, and connection—nearly all core Figma plugin operations. Minor gaps may exist (e.g., bulk variable operations, instance overrides beyond basic), but the set is robust for typical workflows.