“I have a Figma mockup but I don't know how to code it”

Installation

hybrid — cloud-hosted Builder and Figma plugin (Locofy Lightning), with local tools: CLI, VS Code extension, and MCP server to retrieve and merge the generated code.

Prerequisites

A Locofy account (sign-up via Google, GitHub, or email) and an accessible Figma design, by shared URL or via the plugin; for the CLI, Node.js/npm (“npm install -g @locofy/cli”, then “locofy login” and “locofy init”); for MCP, a project synced in the Builder and a per-project generated MCP token.

Hardware

non_applicable

Self-hosting

partial — the platform remains hosted by Locofy, but the generated code belongs to the user and exports (ZIP, GitHub sync, CLI, VS Code extension) to be hosted freely; an on-premise deployment of the platform itself: non_documente.

License

platform license not verified in the official terms consulted; official pages only state that the user keeps full ownership of the generated code.

API & integrations

API: Not documented (no public product REST API is documented in the official sources consulted.) · SDK: Not documented · CLI: yes — official CLI @locofy/cli: “locofy pull” retrieves the generated code and smartly merges it into the local code, then an interactive mode lets you refine it in natural language. · Webhooks: Not documented · MCP: yes — Locofy MCP (@locofy/mcp package) connects the project to compatible editors and agents (Cursor, Claude Desktop/Code, GitHub Copilot, Windsurf, Gemini CLI) via an mcp.json and a project-specific token; component and file retrieval tools documented.

Models

In-house proprietary “Large Design Models” (LDM), multimodal and heuristic, trained on millions of designs and products — without client data. Personal keys (BYOK) and local models: non_documente.

Data

The design is sent to the Locofy service, which converts it with its Large Design Models and sends the code back to the Builder, GitHub, the local machine (CLI/VS Code/MCP); Locofy states it does not use client data to train its models and the user keeps full ownership of the generated code. Retention of designs and code on Locofy's side: non_documente.

Documented limits

Consumption is measured in LDMtokens (Lightning conversion and Agent mode prompts), tracked in the dashboard's “Plan and Usage” page (usage history and balance). Per-plan numeric quotas: non_documente in the official pages consulted.

Operations

Usage and billing tracking (plan, LDMtokens history, invoices) in the dashboard; per-project MCP tokens, regenerable and revocable, with optional expiration (1 month or no expiration). SSO, RBAC, and audit logs: non_documente.

Official sources: www.locofy.ai · www.locofy.ai · www.locofy.ai · www.locofy.ai · www.locofy.ai — verified on November 1, 2026.