figma-mcp-go
Related Servers
Alternatives to figma-mcp-go
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceFigma MCP Bridge is a combined Figma plugin and MCP server that bypasses Figma's free API rate limits by streaming live document data directly to AI tools via a local WebSocket connection instead of the standard cloud API.700MIT
- AlicenseAqualityDmaintenanceWrite-side MCP server for Figma — build, edit, and search Figma designs from Claude Code, Cursor, Cline, or any MCP client. Complements Figma's official read-only MCP with 41 tools for tree creation, variables, components, and visual verification.412MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that simplifies Figma design data, generates code in multiple frameworks, and provides accessibility audits and drift detection, all using a free Figma Personal Access Token without a paid Dev Mode seat.101 npmMIT
- AlicenseAqualityAmaintenanceRead, create, and modify Figma designs programmatically via MCP, empowering AI to execute Figma changes safer, cleaner, and faster.45117 npm11MIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that gives AI agents live access to open Figma files for design handoff and UX writing without API tokens or rate limits.3-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides write access to Figma through the Plugin API, enabling AI agents to create, modify, and manage Figma designs programmatically.23-
TDQS
Scored across 73 tools
Most tools have clearly distinct purposes, but there is some overlap between get_node, get_nodes_info, get_document, get_design_context, get_selection, and get_pages, which could cause confusion for an agent. Similarly, batch_rename_nodes and rename_node, or scan_nodes_by_types and search_nodes, are closely related.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_frame, set_fills, get_pages). The naming is predictable and clear, with no mixing of conventions or ambiguous verbs.
With 73 tools, the server is on the heavier side. While this may be justified given the complexity of Figma (covering design, variables, styles, prototyping), many tools are highly specific (e.g., export_frames_to_pdf, get_fonts) and could potentially be consolidated or omitted.
The tool set covers a broad range of Figma operations: creation, manipulation, styles, variables, prototyping, and exports. However, there are minor gaps, such as lacking a dedicated update_variable tool (though set_variable_value exists) and no support for shared styles or library components.