Skip to main content
Glama
arimunandar

figsnap-mcp

by arimunandar

Related Servers

Alternatives to figsnap-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      214 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables local MCP-capable assistants to connect to Figma Desktop to read documents, pages, and selections, edit native layers and components, and export PNG/SVG across multiple files without Figma API keys.
      2
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access Figma design context, generate code from frames, extract variables, components, and layout data, and create or modify Figma files directly from MCP clients.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects an MCP client such as Claude Code to the Figma file open in the desktop app, letting the agent create frames, write text, apply styles, import images and SVGs, take screenshots, and run arbitrary Figma Plugin API code. Commands travel through a local development plugin instead of Figma's web API, so there are no tokens, quotas, or rate limits.
      59 npm
      3
      MIT
    • 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.
      3,295 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to read and edit the file currently open in Figma Desktop through a local development plugin, supporting node inspection, JSON/image exports, and arbitrary Plugin API scripts without REST API rate limits.
      7
      15 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 39 tools

    Disambiguation3/5

    Descriptions are detailed and usually point to distinct purposes, but several tools overlap: figma_list_saved duplicates the list action of figma_saved, and get_tree/get_children/find_nodes plus set_fill/apply_style/bind_variable all occupy nearby territory. An agent could easily pick the wrong one without reading the full descriptions carefully.

    Naming Consistency3/5

    Most tools follow figma_verb_noun (create_frame, set_fill, get_children), but there are clear outliers: figma_saved, figma_pages, and figma_component_properties omit verbs, and select/extract/group are verb-only. The pattern is readable but not enforced.

    Tool Count2/5

    39 tools is well past the 25+ threshold and will tax an agent's selection and context budget. Many setters (fill, stroke, text, effects, bounds, layout) could arguably be consolidated without losing clarity.

    Completeness4/5

    CRUD coverage for design nodes is strong: create, read via tree/children/find, update through many setters, delete, plus export, bookmarks, styles, variables, and versioning. Minor gaps remain—no direct get-node-by-id, no component/style creation—but agents can work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues