Skip to main content
Glama
Sign In
Layerwright

Layerwright

by shayan-m81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Layerwright

  • Talk to Figma MCP

    grab
    A
    license
    B
    quality
    D
    maintenance
    An MCP server integration that enables Cursor AI to communicate with Figma, allowing users to read designs and modify them programmatically through natural language commands.
    19
    1,268 npm
    7,076
    MIT

  • Figma MCP

    alucardeht
    A
    license
    A
    quality
    D
    maintenance
    Enables interaction with Figma files through intelligent API access, providing navigation, asset extraction, and design token retrieval with 95% token-optimized compact tree output format.
    15
    1
    MIT

Related Servers

  • figma-free-mcp

    haju-xp
    A
    license
    B
    quality
    B
    maintenance
    Enables Claude to connect to Figma without a paid plan, offering auto-connect and 100+ tools for document manipulation, design system sync, and code-to-Figma conversion.
    100
    86 npm
    1
    MIT

  • Figma Console MCP Server

    Baskaran03528
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables Claude to interact directly with Figma Desktop for creating UI components, managing design tokens, and auditing files through natural language. It establishes a live connection between the AI and the Figma API via a local server and companion plugin.
    14,295 npm
    MIT

  • chalk

    rizaardiyanto1412
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables Claude Code in any project to read canvas frames, screenshots, and design guidelines so it can build the designs in code.
    631,444,011 npm
    MIT
Deploy Server
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A3.5/5.0

Scored across 22 tools

Disambiguation4/5

Most tools target a distinct stage of the Figma workflow (status, scan, inspect, plan/preview/execute, verify, analyze/apply, edit, migrate). A few boundaries blur, notably figma_import_html vs import_html_to_plan and the all-in-one figma_edit overlapping with specialized ops like figma_apply_transformations and figma_migrate, but descriptions differentiate them well.

Naming Consistency4/5

Names are predominantly consistent snake_case with subsystem prefixes (figma_*, code_*, layerwright_*), which reads predictably. The outlier import_html_to_plan breaks the figma_ prefix used by its sibling figma_import_html, and a few tools are bare verbs (figma_inspect, figma_verify), a minor deviation.

Tool Count4/5

22 tools sits in the heavy range, but the scope (Figma bridge, design-system scan/foundations, plan preview/execute/verify, HTML import, code mapping) is genuinely broad and most tools earn their place. Slightly over-stuffed, with the two HTML-import tools and the mega figma_edit the main candidates for consolidation.

Completeness4/5

The surface covers a full design-to-code lifecycle: status/cleanup, DS scan and foundations, node inspection, plan preview/execute/verify, non-destructive analysis/apply, editing, migration, image export, selection, project memory, and code scan/mapping/verification. Gaps are minor, e.g. no explicit design-system element deletion or standalone code-generation output tool.

Maintenance

ActivityMaintained
ResponsivenessLimited data

Resources