# Lottie Creator for AI agents

Lottie Creator (https://creator.lottiefiles.com) is a browser-based editor for Lottie and
dotLottie animations, built by LottieFiles. This page explains how an agent should work
with it. The short index is at /llms.txt; authentication is covered in /auth.md.

## What Creator is

- A single-page web application. The homepage is the editor itself, so fetching the HTML
  returns an app shell plus the static summary in this document. The only other endpoint
  on this domain is `/og`, which renders share-card images; there is no public API here.
- Animations are edited in a scene with layers, shapes, keyframes, state machines, themes,
  and segments, then exported as Lottie JSON, dotLottie (.lottie), GIF, MP4, or Telegram
  stickers, or saved to a LottieFiles workspace.
- Guest mode allows editing without an account. Saving to a workspace, exporting, and
  publishing require a LottieFiles account (free plan available, see
  https://lottiefiles.com/pricing).

## Entry points

| URL                                               | Purpose                                                                                                         |
| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| `https://creator.lottiefiles.com/`                | Open the editor with an empty scene.                                                                            |
| `https://creator.lottiefiles.com/?agent=1`        | Open the editor and defer the welcome modal, guided tour, questionnaire, and announcements for the tab session. |
| `https://creator.lottiefiles.com/?remixId=<code>` | Open a publicly shared animation as a remix.                                                                    |
| `https://creator.lottiefiles.com/?fileId=<id>`    | Open a file from the signed-in user's LottieFiles workspace.                                                    |

## Three ways to operate Creator

### 1. Creator MCP (local stdio server)

Best for coding agents and desktop assistants. The server runs on the user's machine and
talks to a Creator tab open in their browser.

```json
{
  "mcpServers": {
    "lottiefiles-creator": {
      "command": "npx",
      "args": ["-y", "@lottiefiles/creator-mcp@latest"]
    }
  }
}
```

Prerequisites: Node.js 18 or later, an MCP-compatible client, and
https://creator.lottiefiles.com open in the browser. The tools are the same typed native
tools Motion Copilot uses, so the agent never executes arbitrary scripts inside the
editor. Examples: `read_scene`, `list_scenes`, `create_shape`, `create_text`, `set_fill`,
`set_stroke`, `apply_keyframes`, `read_keyframes`, `animate_entrance`,
`apply_motion_preset`, `add_state_machine`, `add_state`, `add_transition`, `add_theme`,
`create_slot`, `import_asset`, `vectorize_image`.

Setup guide and client-specific instructions:
https://docs.lottiefiles.com/en/creator/13_ai-tools/lottie-creator-mcp.md

### 2. WebMCP (in-page tools)

Best for browser agents. In a WebMCP-capable Chrome (origin trial, or
`chrome://flags/#enable-webmcp-testing`), Creator registers tools on
`document.modelContext` once the editor has loaded:

| Tool                                                                     | Purpose                                                                                            |
| ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- |
| `discover_tools`                                                         | Return descriptions, JSON input schemas, and TypeScript signatures for named native tools.         |
| `execute_typescript`                                                     | Run TypeScript against the native tools with CodeMode (sandboxed QuickJS). Use this for mutations. |
| `read_scene`, `list_scenes`                                              | Read scene data, layers, the current selection, and available scenes.                              |
| `read_keyframes`, `list_layer_effects`                                   | Inspect a layer's animation and effects.                                                           |
| `measure_text_units`, `list_fonts`                                       | Measure text and inspect the font catalog.                                                         |
| `list_themes`, `list_slots`, `list_motion_system_items`                  | Inspect themes, slots, and reusable motion items.                                                  |
| `list_segments`                                                          | Inspect timeline segments.                                                                         |
| `list_state_machines`, `list_states`, `list_interactions`, `list_inputs` | Inspect interactive animation configuration.                                                       |

The first schema-valid WebMCP call defers startup prompts, so an agent does not have to
dismiss the onboarding UI. Users can turn WebMCP off under Settings → MCP Settings.

### 3. Hosted LottieFiles MCP (remote)

For searching and managing animations in a LottieFiles account rather than editing a
scene: `https://mcp.lottiefiles.com/mcp` (Streamable HTTP, OAuth 2.1 with PKCE).
Documentation: https://docs.lottiefiles.com/en/platform/mcp.md

## Recommended workflow

1. Read before writing: call `read_scene` (and `read_keyframes` for animated layers) so
   edits are relative to the authored values.
2. Discover schemas before using an unfamiliar tool (`discover_tools` over WebMCP, or the
   tool list in your MCP client).
3. Make the smallest change that satisfies the request: easing-only, then retiming, then
   amplitude, then rebuild.
4. Verify the result by reading the scene back; a tool call that did not throw is a write,
   not proof of motion.
5. Leave the playhead on a frame where the result is visible (`set_current_frame`).

## Limits and safety

- Tools act on the scene in the user's open tab; they do not bypass authentication,
  consent prompts, or required confirmations.
- Creator does not expose account, billing, or library operations through its tools; use
  the hosted LottieFiles MCP for those.
- Telemetry for MCP and WebMCP is consent-controlled and contains no scene content, tool
  inputs, or results.

## More

- Creator documentation: https://docs.lottiefiles.com/en/creator/index.md
- Creator API and plugins: https://docs.lottiefiles.com/en/creator-api/index.md,
  https://docs.lottiefiles.com/en/creator-plugins/index.md
- Agent skill:
  https://creator.lottiefiles.com/.well-known/agent-skills/lottie-creator/SKILL.md
- Discovery catalogs: https://creator.lottiefiles.com/.well-known/ard.json,
  https://creator.lottiefiles.com/.well-known/api-catalog
- Help Center: https://help.lottiefiles.com/