Skip to main content
Glama

Related Servers

Alternatives to figmcp

No user-submitted related servers found.

    Related Servers

    • 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
      76 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables any MCP client to drive the real Figma Desktop plugin API through one local daemon, so agents can read and edit the open file, take screenshots, export assets, and inspect variables, components, and styles. Everything stays on 127.0.0.1 with no cloud, API keys, or Dev/Full seat required.
      506 npm
      1
      MIT
    • 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

    TDQS

    A4.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target a distinct resource or action, and the descriptions actively steer the agent (e.g. get_metadata says 'Always prefer get_design_context', get_variable_defs distinguishes tokens from layout). The main overlaps are get_design_context also returning a screenshot and assets, which get_screenshot/download_assets cover separately, and import_design_export vs save_design_export, which could momentarily confuse direction. These are minor and well documented.

    Naming Consistency4/5

    The set mostly follows a snake_case verb_noun convention (get_*, add_*, remove_*, import_*, save_*, download_*, search_*, place_*, verify_*), which is readable and predictable. Outliers are whoami (no verb_noun form) and the vaguely named use_figma, but overall consistency is strong.

    Tool Count5/5

    15 tools sit right at the upper end of the well-scoped range and each earns its place: read/context, screenshots, assets, variables, design-system search, code-connect CRUD, snapshots, write/edit, and verification. Nothing appears redundant filler or missing from a reasonable budget.

    Completeness4/5

    The surface covers a full design-to-code lifecycle: inspect (context, metadata, screenshot, variables, assets), search the design system, manage code-connect mappings (get/add/remove), import/save snapshots, write designs (use_figma, place_image), and verify code. Minor gaps remain, such as no explicit snapshot deletion/listing tool despite snapshots being replaceable, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues