Figma Console MCP Server
Related Servers
Alternatives to Figma Console MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to access and manipulate Figma designs, including extracting design systems, creating and debugging UI components, and syncing design tokens bidirectionally.16,945 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, create, and modify Figma designs, synchronize design tokens bidirectionally, and auto-document component-variant sets via Obra Autodocs integration.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, analyze, and modify Figma designs, including bulk style updates, accessibility audits, comment triage, and code generation from designs.807 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read and modify Figma designs programmatically, supporting design analysis, element creation, text replacement, annotations, auto-layout configuration, and prototype visualization through natural language commands.1,908 npmMIT
- AlicenseBqualityBmaintenanceEnables AI assistants to read, analyze, and modify Figma designs, manage design tokens, and create prototype connections, all while keeping data local.6315 npm10MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Figma designs programmatically, supporting comprehensive design automation including text manipulation with formatting preservation, batch operations, prototyping, auto-layout configuration, and component management.7519 npm5MIT
TDQS
Scored across 130 tools
The surface contains many near-duplicate tools whose boundaries require reading long descriptions to resolve: figma_take_screenshot vs figma_capture_screenshot vs figma_get_component_image, figma_get_file_data vs figma_get_file_for_plugin vs figma_get_file_at_version, figma_get_variables vs figma_get_token_values vs figma_get_design_system_kit, and figma_diff_versions vs figma_get_changes_since_version vs figma_get_design_changes. Many descriptions even contain explicit 'NOT this, use that instead' disclaimers, which is a strong signal of inherent overlap rather than distinct purposes.
Nearly everything follows the prefixed snake_case verb_noun pattern (figma_get_*, figma_create_*, figma_set_*, figjam_create_*), with domain prefixes figma_/figjam_ used coherently. Minor deviations exist (figma_execute, figma_diagnose, figma_ds_analyze, figma_manage_animation_styles, figma_lint_design), but they remain readable and predictable.
130 tools in a single server is far beyond a manageable set for an agent to select from, spanning unrelated domains (Slides, FigJam, variables/tokens, motion, shaders, version history, code accessibility, design-system extraction). This is effectively six or seven servers bundled into one and will cause context bloat and misselection regardless of individual tool quality.
Coverage of the Figma domain is genuinely broad: variables and modes have full CRUD plus batch and token import/export, slides have create/delete/duplicate/reorder/content, FigJam has create/read/arrange, comments have get/post/delete, and version history has list/diff/blame/changelog. Remaining gaps are minor, such as no comment update/edit tool and no style creation or deletion counterpart to figma_get_styles.