No user-submitted related servers found.
Scored across 112 tools
With 112 tools, there are a few clusters that could confuse an agent, such as the multiple node-reading tools (get_document, get_node, get_nodes_info, get_design_context, get_selection) and the mapping tools (component_map, icon_map, token_map). However, each tool's description clearly delineates its specific purpose and usage context, so the overlap is mostly resolvable. Overall, the tools are distinct enough for a careful agent.
The vast majority of tools follow a consistent verb_noun pattern (create_frame, set_fills, get_node, delete_nodes, rename_page, apply_animation_style). A few deviations exist, such as token_map, component_map, icon_map, design_diff, and the bare verb batch, but these are minor and do not significantly hinder predictability. The naming convention is coherent overall.
At 112 tools, this server is far beyond the typical well-scoped range and exceeds the 50-tool threshold for an extreme mismatch. While the Figma design-to-code domain is broad, the tool set could likely be consolidated or organized into sub-modules to reduce cognitive load. The sheer number makes it unwieldy for an agent to discover and select the right tool.
The tool set covers the full lifecycle of Figma operations: node CRUD, styling, text, variables, styles, components, prototypes, motion, exports, and project mapping. Minor gaps exist, such as no delete_variable_mode or rename_variable_collection, and no explicit tool to read variable bindings in isolation (though get_design_context provides this). Overall, the surface is remarkably complete for the domain.