Skip to main content
Glama
Rompni

figma-rest-mcp

by Rompni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to figma-rest-mcp

No user-submitted related servers found.

    Related Servers

    • figma-mcp-express

      sunhome243
      A
      license
      Not graded
      quality
      A
      maintenance
      Fast, quota-free Figma automation for coding agents, enabling AI agents to read, edit, migrate, audit, screenshot, and prototype inside Figma Desktop files.
      8
      MIT

    • figma-mcp

      Anakintano
      F
      license
      B
      quality
      D
      maintenance
      Enables AI agents to read, inspect, and export Figma designs programmatically. Provides tools for listing components, styles, and exporting assets in various formats.
      5
      1
      -

    • AllCrew Figma Workspace MCP

      mal4i6ka
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read the live state of an open Figma file — variables, modes, components, prototype edges and assets — and to export design tokens and code packages for web, iOS, Android, React, Django and Tauri through a user-run loopback bridge with separate read and write gates.
      2
      MIT

    • Fimake

      chavisnguyen
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read, create, edit, and organize Figma documents directly through a local plugin bridge, without needing a Figma AI subscription.
      2
      Apache 2.0

    • 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.
      356 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target a unique resource and action, and descriptions explicitly cross-reference sibling functions (get_images vs get_image_fills, get_variable_defs vs fallbacks). However, the variable/token helpers and design-to-code utilities overlap closely enough that an agent could still pick the wrong one without careful attention.

    Naming Consistency3/5

    The majority use snake_case verb_noun names, but conventions are mixed: list_projects vs get_team_components, post_comment vs create_dev_resources, singular/plural dev_resource(s), plus non-standard utility names like whoami, find_nodes, extract_text, and suffix-based helpers (_lite, _fallback).

    Tool Count2/5

    41 tools is well beyond the comfortable range and spans many subdomains such as files, nodes, images, comments, libraries, variables, dev resources, and webhooks. This would be more manageable as several focused MCP servers.

    Completeness5/5

    The server covers the major Figma REST surface: file/project/team reads, node inspection, rendering, images, comments/reactions, component/style libraries, variables, dev resources, and webhook CRUD. Mutation-capable resources have read/write/update/delete covered, so agents are unlikely to hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources