Use Lami with confidence

Sign up with an email you control. Organizations group billing, members, and projects; invite collaborators once your workspace is stable.

If your organization requires admin approval for new members, wait for the approval email before expecting shared project access.

Every project row persists across onboarding and post-wizard work—there is no duplicate “workspace project.” The wizard captures references, palette intent, and structural cues.

You can leave and return: incomplete onboarding appears under continue-setup surfaces until the Theme reaches the complete state required for workspace entry.

Dashboard “active” lists and OpenDrive import targets only include projects that are active, finished onboarding, and have a completed Theme. Draft rows remain addressable for continue-setup flows.

This distinction prevents half-baked configurations from appearing where teams expect production-ready assets.

The workspace hosts canvas tools, background workflows, and Object Lab boards tied to the same project id. Media libraries deduplicate references so prompts stay short while intent stays rich.

Offline or flaky networks: some surfaces queue saves; watch the UI for retry states and avoid closing tabs mid-upload.

Generation calls route through Lami’s provider integrations. Streaming and model availability may differ per capability; admins see aggregate usage while members see project-scoped indicators.

Do not send regulated health, financial, or personally identifying client data through prompts unless your agreement explicitly permits it. When unsure, ask via Contact before processing.

For product questions, billing, or privacy requests, use the Contact form. Include reproduction steps and timestamps when reporting generation failures—our logs attach request identifiers that speed triage.

For security vulnerabilities, disclose responsibly through the same channel with “SECURITY” in the subject line.

Lami ships continuously behind feature flags. User-visible changes land when they are stable for production orgs; experimental toggles may preview earlier in controlled environments.

This document updates when customer-facing behavior changes; engineering epics in the repository are not contractual commitments.

MCP is how Cursor, Claude Code, or other clients call Lami Studio tools (theme_create, theme_items_create_job, theme_characters_create_job, and so on). You need two separate setup steps on this page: MCP connection (this section) and the Agent Skill install (next section).

Step 1 — API key: In lami.design go to Organization → API keys and create a Studio key (lami_live_…). Use themes:read to inspect themes and jobs; themes:write to run pipelines.

Step 2 — MCP URL: Production is https://lami.design/api/mcp (the path is /api/mcp, not /mcp alone). Local development uses http://127.0.0.1:3030/api/mcp after you run bun run dev:mcp in the Lami repository.

Step 3 — Cursor config: Add the server block below to ~/.cursor/mcp.json (user-wide) or your project’s .cursor/mcp.json. Set export LAMI_API_KEY=lami_live_… in the shell that launches Cursor, or add the same variable under Cursor Settings → Tools & MCP → Environment. Restart Cursor so the server loads.

Step 4 — Verify: In chat, ask the agent to list MCP tools or read the studio://agent-workflow resource. Members can also open Studio Playground at /dashboard/studio/playground (session login, same tools as MCP).

# Production MCP
URL: https://lami.design/api/mcp
Header: Authorization: Bearer lami_live_<your-key>

# ~/.cursor/mcp.json (merge into mcpServers)
{
  "mcpServers": {
    "lami-studio": {
      "url": "https://lami.design/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:LAMI_API_KEY}"
      }
    }
  }
}

# Local dev (Lami repo): bun run dev:mcp  →  http://127.0.0.1:3030/api/mcp
# Optional helper: bun run dev:mcp:setup

The lami-studio skill is a hub-and-spoke bundle: SKILL.md (overview, cold start, recipes, rules) plus reference files (async-jobs, contracts, vfx-pipeline, mcp, api, sdk). It does not replace MCP — complete section 8 first.

Prerequisites: Studio API key (lami_live_…) and MCP server configured.

Install from any project:

npx skills add unsanityinc/lami --skill lami-studio -y

Global install: add -g. Local Lami clone: run at repo root with npx skills add . --skill lami-studio -y

After MCP + skill: read studio://agent-workflow, run studio_discover, then studio_recipe with new_theme_then_items. Required reading: async-jobs.md (every create_job returns 202 until wait_job reaches ready).

# Project (requires GitHub access to unsanityinc/lami)
npx skills add unsanityinc/lami --skill lami-studio -y

# All projects
npx skills add unsanityinc/lami --skill lami-studio -y -g

# Local clone — run at Lami repo root
npx skills add . --skill lami-studio -y

# Bundle files installed to .cursor/skills/lami-studio/
# SKILL.md, async-jobs.md, contracts.md, vfx-pipeline.md, mcp.md, api.md, sdk.md, dev-mcp-scripts.md