Skip to main content
Glama
irshadio

figmcp

by irshadio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to figmcp

No user-submitted related servers found.

    Related Servers

    • localfig

      LucasGorgal
      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
      40 npm
      1
      MIT

    • figma-meta-mcp

      shinjiyu
      A
      license
      A
      quality
      C
      maintenance
      Figma MCP server that lets agents execute arbitrary JavaScript inside a running Figma desktop app via a local development plugin, enabling real-time document inspection and manipulation while avoiding REST API rate limits.
      3
      MIT

    • cyber-figma

      cyberuni
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (editing via use_figma, reading via get_design_context/get_metadata/get_screenshot, asset download, code-connect mapping). The main overlap risk is among the read/inspect tools (get_design_context, get_metadata, get_variable_defs, get_screenshot, download_assets) and between the export/snapshot tools (save_design_export, import_design_export, download_assets), though descriptions explicitly steer usage (e.g. 'Always prefer get_design_context').

    Naming Consistency4/5

    Nearly all tools follow a verb_noun snake_case pattern (get_design_context, add_code_connect_map, search_design_system, place_image, download_assets, verify_code). The lone outlier 'whoami' breaks the convention, a minor deviation in an otherwise predictable scheme.

    Tool Count5/5

    15 tools is at the top of the well-scoped range and each maps to a distinct capability (edit, inspect, verify, assets, mappings, status). No filler tools; the count fits a design-to-code Figma integration.

    Completeness4/5

    The surface covers the full lifecycle: design export/snapshot (save/import), code-connect mapping (add/get/remove), reading (context, metadata, screenshot, variables, design system search), editing (use_figma, place_image), verification (verify_code), and asset download. Minor gaps exist (e.g. no dedicated snapshot listing/removal tool beyond whoami), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources