No user-submitted related servers found.
Scored across 73 tools
Many tools have heavily overlapping purposes: scene information is split across get_basic_info, get_tree_summary, inspect_scene_context, get_node_info, get_children, query_nodes, and find_nodes, while mutations are scattered across apply_node_patch, apply_document_transaction, update_styles, set_text_content, rename_nodes, and move_nodes. The detailed descriptions help, but the boundaries are blurry enough that an agent could easily select the wrong tool.
Tool names overwhelmingly follow a clear verb_noun snake_case pattern (create_artboard, get_node_info, set_tokens, export_combined_pdf). Minor deviations exist—bare 'export', 'write_html' with lowercase noun, and compound verbs like 'autofix' and 'batch_write'—but these do not seriously undermine the predictable naming convention.
With 73 tools, this server far exceeds even the 50+ extreme-mismatch threshold. While the server covers a broad design domain, the sheer number of tools bloats context, complicates selection, and creates unnecessary overlap; a more focused surface of 15-25 tools would likely cover the same workflows more coherently.
The server provides deep coverage of node lifecycle, styles, design tokens, comments, checkpoints, export formats, responsive/generation, QA checks, and file/page management. Obvious gaps remain—no file deletion/rename, no page deletion, and no way to create or reply to comment threads—but core design-automation workflows are well represented.