Skip to main content
Glama
Rachit0-glitch

figma-custom-mcp

by Rachit0-glitch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to figma-custom-mcp

No user-submitted related servers found.

    Related Servers

    • figma-bridge

      huaer9000
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables stdio MCP clients such as Cursor and Claude Code to read and modify the currently open Figma Desktop file, export selected nodes as local PNG/SVG files, and create or edit basic canvas nodes using precise layout data for pixel-level reconstruction.
      2,243 npm
      1
      MIT

    • figma-local-bridge

      A1tolia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and modify the currently open Figma design file through a paired local Figma plugin, supporting operations like creating nodes, editing properties, and exporting PNG/SVG.
      162 npm
      1
      MIT

    • figma-ui-mcp

      kiettt8-product
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.
      10
      222 npm
      MIT

    • pholly-figma-mcp

      mubzie
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP bridge for live Figma documents, enabling design inspection, editing, asset export, component authoring, and variable management through a plugin and WebSocket server without consuming Figma REST API requests.
      1
      MIT

    • figmma

      stuffbucket
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with the Figma API through MCP tools for managing files, projects, and comments, plus a real-time observability dashboard.
      7
      11 npm
      2
      ISC

    • figmingo-mcp

      wenym8
      A
      license
      A
      quality
      B
      maintenance
      Local-first Figma MCP server providing unlimited read access via Personal Access Token, HTML replica generation with parity verification, and write-to-canvas through a companion plugin bridge.
      15
      35 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

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a distinct action (delete, reorder, export, status, design/create, read, patch). The only potential overlap is between figma_design and figma_patch_node, but design is for initial creation/sync while patch is for targeted updates, so the boundary is clear.

    Naming Consistency4/5

    All tools use the prefix 'figma_' followed by a descriptive verb_noun pattern (e.g. figma_delete_node, figma_reorder_node). The only minor inconsistency is the verb choice: 'screenshot' is less typical than 'export', and 'status' is a noun rather than an action, but overall the pattern is clear and predictable.

    Tool Count5/5

    7 tools is well-scoped for a Figma design tool MCP server. Each tool covers a core operation (CRUD, reorder, export, status) without being too many to navigate or too few to be useful.

    Completeness4/5

    The server covers essential operations: create (via figma_design), read (figma_node), update (figma_patch_node, figma_reorder_node), delete (figma_delete_node), and export (figma_screenshot). A minor gap is the lack of a dedicated tool for listing node children or searching nodes, but the read tool with nodeId omission provides a reasonable workaround.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources