No user-submitted related servers found.
Scored across 188 tools
With 188 tools there are many overlapping purposes: figma_set_solid_fill vs set_fill_color both set solid fills, and text-setting is split across figma_set_text, set_text_content, set_multiple_text_contents, and create_text. Reaction tools (set_reactions, upsert_reaction, set_transition_reaction, set_smart_animate_reaction) and instance-creation tools (create_instance_from_component_key, create_instance_from_set_key, create_instance_from_instance, create_component_instance) also have fuzzy boundaries. Descriptions help, but an agent will frequently misselect.
The vast majority follow a predictable snake_case verb_noun pattern (create_frame, set_padding, get_node_info, delete_variable). Minor deviations exist: a handful of tools carry a figma_ prefix (figma_set_solid_fill, figma_bridge_status) and a few are not strictly verb_noun (boolean_group, combine_as_variants), but overall it is readable and consistent.
188 tools is an extreme mismatch for any single server surface, far beyond the 50+ threshold that indicates an unwieldy set. Even for a rich domain like Figma, this volume forces the agent to navigate a huge catalog and increases the chance of picking the wrong tool.
The surface covers an enormous breadth: node CRUD, fills/strokes/effects, text, auto-layout and grid, variables/tokens, components and slots, prototyping reactions and motion, styles, comments, exports, and events. Nearly every design workflow has a corresponding operation, with no obvious dead ends.