Ligma: a better Figma MCP tool / CLI command for coding agents

CLI alternative to the Figma MCP. Fetches a Figma node and emits a deterministic, token-efficient artifact bundle optimized for code agents.

The problem it sets out to solve: helping agents make sense of the things they need to know to implement a design. Figma json is geared towards accurately recording document structure, not revealing intent and guiding implemention.

Files are downloaded to disk instead of dumped into the agent's context window (./artifact by default, but can be specified), and can list / download additional assets (as png or svg).

Made with spec-driver.

Install

npm install -g ligma-mcp

Or from source:

git clone https://github.com/davidlee/ligma && cd ligma
pnpm install && pnpm build && pnpm link --global

Requires Node >= 18.

MCP server setup (Claude Code)

claude mcp add ligma -- ligma mcp

Requires FIGMA_TOKEN in your shell environment. Alternatively, pass it explicitly:

{
  "mcpServers": {
    "ligma": {
      "command": "ligma",
      "args": ["mcp"],
      "env": {
        "FIGMA_TOKEN": "your-figma-token"
      }
    }
  }
}

6 tools: figma_get_node, figma_get_outline, figma_get_render, figma_list_assets, figma_get_asset, figma_get_assets.

Usage

export FIGMA_TOKEN="<your-figma-personal-access-token>"

ligma <figma-url>

Or pass the token inline:

ligma <figma-url> --token <token>

Note: it takes a hot minute and there's no feedback during download. Little spinner coming soon (ironic, eh?).

Subcommands

list-assets

List detected export targets as JSON:

ligma list-assets <figma-url>

Outputs a JSON array of { nodeId, name, format, reason } to stdout.

get-asset

Fetch a single asset by node ID and write to disk:

ligma get-asset <figma-url> <node-id>

Writes the asset file and prints the absolute path to stdout.

Options

Project documentation

• Technical brief
• PROD-001 — Figma fetch and normalization pipeline

Design revisions