Skip to main content
Glama
musepy
by musepy

Related Servers

Alternatives to genable-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server exposing Figma REST API tools to AI agents, enabling file reads, comments, variables, and other resource operations. Works with personal access tokens and integrates with Claude, Cursor, Codex, and more.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Open-source, bidirectional Figma agent for MCP clients — a free alternative to Figma's Dev Mode MCP. Reads designs with high-fidelity grounding and writes back to the canvas: frames, text, auto-layout, styles, variables, and components. 92 tools, no API token, no paid Figma seat.
      112
      1,001
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      The Figma desktop app as an MCP server. Gives AI agents the full Figma Plugin API on your open file: read, write, tokens, components, exports, undo. Runs locally with no cloud API, no token and no quota.
      10
      47 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read and write Figma designs through a local WebSocket relay, turning Figma selections into framework-aware code and building/editing designs directly on the canvas. Provides 112 MCP tools for bidirectional design-code workflows with support for any MCP client.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Figma MCP server with full read/write access via plugin bridge — no API token, no rate limits. 83 tools for design automation: styles, variables, components, prototypes, and content.
      15
      MIT

    TDQS

    A3.9/5.0

    Scored across 41 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose with detailed descriptions. Tools with overlapping functionality (e.g., edit vs. setters) are explicitly differentiated by usage guidance.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., add_component_prop, bind_variable, create_vector). No mixing of conventions.

    Tool Count3/5

    41 tools is high but justified by the broad scope of Figma design operations. However, it exceeds the typical well-scoped range (3-15), feeling somewhat heavy.

    Completeness4/5

    Covers CRUD for nodes, components, variables, and provides audit, user interaction, and session management. Minor gaps exist (e.g., no explicit ungroup tool), but most workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues