Skip to main content
Glama
Henry-Hong

figma-mcp

by Henry-Hong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to figma-mcp

No user-submitted related servers found.

    Related Servers

    • figma-mcp

      chisanucha-suwan
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only Figma MCP server that enables design-to-code workflows by talking to the Figma REST API with a personal access token, for use with Claude Code and GitHub Copilot.
      1,330
      MIT

    • cyber-figma

      cyberuni
      A
      license
      Not graded
      quality
      A
      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

    • genable-mcp

      musepy
      A
      license
      A
      quality
      C
      maintenance
      Write-side MCP server for Figma — build, edit, and search Figma designs from Claude Code, Cursor, Cline, or any MCP client. Complements Figma's official read-only MCP with 41 tools for tree creation, variables, components, and visual verification.
      41
      1
      MIT

    • figma-mcp

      tioramadhn
      F
      license
      Not graded
      quality
      C
      maintenance
      Custom MCP server for the Figma REST API that enables inspecting file structures, nodes, styles, components, variables, and exporting images, with optional comment posting. It is read-only except for posting comments and is designed for use with Claude Code.
      1,330
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool addresses a recognizable retrieval need—structure, metadata, design styles, screenshots, variables, and prototype flows—so misselection is unlikely. The main fuzziness is between get_metadata and get_design_context, but their descriptions separate generic node metadata from design-specific context.

    Naming Consistency5/5

    All seven tools use the exact get_<resource> snake_case convention with no verb changes or mixed styles. This makes the API surface highly predictable.

    Tool Count5/5

    Seven focused read-only retrieval tools is well within the ideal range for a Figma context server. Each tool covers a distinct aspect of design exploration without redundancy or bloat.

    Completeness4/5

    The set covers structure, node metadata, design context, screenshots, variables, and prototype flows, which covers the core read/analysis workflows. It does not include mutation or collaboration features, but the get_* surface appears intentionally scoped rather than incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources