Skip to main content
Glama
southleft

figma-console-mcp

by southleft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to figma-console-mcp

No user-submitted related servers found.

    Related Servers

    • Figma Console MCP

      DexMachina-Design
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server that bridges design and development, giving AI assistants complete access to Figma for extraction, creation, debugging, and bidirectional token sync.
      79,756 npm
      MIT

    • Figma MCP Server

      1yhy
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that integrates Figma design files with AI coding tools like Cursor, Windsurf, and Cline, allowing AI tools to access and understand Figma design data for generating more accurate code.
      178 npm
      31
      MIT

    • Figma MCP Write Bridge

      firasmj
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to programmatically create, modify, and manage Figma documents via a WebSocket bridge and Figma plugin.
      11
      6
      MIT

    • Talk to Figma MCP

      Alkaness
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read, inspect, and edit Figma files through a Model Context Protocol server with 107 tools, visual snapshots, fidelity tools, and optional REST API access.
      20 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 130 tools

    Disambiguation2/5

    Several tools overlap heavily in purpose, especially screenshot/capture tools (figma_take_screenshot, figma_capture_screenshot, figma_get_component_image), component inspection tools (figma_get_component, figma_get_component_for_development, figma_get_component_for_development_deep, figma_analyze_component_set), and variables/token retrieval tools (figma_get_variables, figma_get_library_variables, figma_get_token_values, figma_get_design_system_kit). Descriptions help somewhat, but the boundaries between these retrieval tools are unclear enough that an agent could easily choose the wrong one.

    Naming Consistency4/5

    Most tools follow a predictable snake_case pattern with a domain prefix and verb-oriented action (figma_get_*, figma_create_*, figma_set_*, figjam_create_*, figma_ds_*). There are minor deviations such as figma_take_screenshot vs. figma_capture_screenshot and some awkward names like figma_get_design_system_kit, but the overall convention is readable and stable.

    Tool Count1/5

    130 tools is far beyond what is reasonably scoped for a single MCP server, even one covering as broad a domain as Figma design systems, FigJam, and Slides. The surface is sprawling and includes many niche, overlapping, or workflow-specific tools that should likely be consolidated or split into separate servers.

    Completeness4/5

    The server covers an unusually broad lifecycle: variables/tokens, components, node manipulation, comments, version history, accessibility, FigJam, Slides, animations, and shaders. There are still some gaps, such as limited local style creation/editing and no explicit effect-style management, but these are workaroundable via figma_execute and do not represent severe missing operations.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources