LottieFiles Creator MCP – Motion Design Automation
The official LottieFiles Creator MCP server gives AI assistants direct access to the Lottie Creator API through a local bridge. Use it to create and modify motion graphics, generate variants, inspect animation quality, and automate production-ready Lottie workflows.
Overview
The official LottieFiles Creator MCP connects MCP-compatible AI assistants to LottieFiles Creator, a browser-based motion-design environment for lightweight and interactive animations. The local MCP bridge lets an assistant work with the live Creator document so it can build or modify animations from natural-language instructions instead of relying only on static prompts or exported files.
What the MCP server enables
LottieFiles documents broad access to the Creator API. With the Creator browser tab open and MCP enabled, an AI assistant can:
- Create scenes with defined dimensions, duration, frame rate, and names.
- Add, organize, rename, lock, focus, and edit animation layers.
- Create and update shapes, fills, strokes, text, transforms, and keyframes.
- Adjust timing, easing curves, colors, visibility, and other animation properties.
- Import Lottie JSON, dotLottie, SVG, and image assets.
- Export scenes as Lottie JSON.
- Generate multiple animation variants for themes, sizes, or brand palettes.
- Analyze motion for contrast, pacing, consistency, accessibility, and brand alignment.
- Read the current state of an open Creator file and apply changes in real time.
When to use it
Use the LottieFiles Creator MCP when an AI-assisted workflow needs to produce or refine motion assets directly inside Creator. Practical uses include generating loaders and progress indicators, creating UI micro-interactions, preparing light and dark variants, adjusting timing across a scene, building branded animation systems, and converting a written motion brief into editable layers and keyframes.
It is also useful when designers and developers want to generate animation assets while working in coding or AI tools such as Claude, Cursor, Windsurf, VS Code, or other MCP-compatible clients.
Connection and authentication
The official server runs locally over stdio with Node.js 18 or later:
npx -y @lottiefiles/creator-mcp@latest
No API key or static authorization header is documented for this connection. Instead, the local package communicates with the active LottieFiles Creator browser tab. The user must keep Creator open, navigate to Settings → MCP Settings, and enable MCP for the session.
Key considerations
The Creator tab must remain open because the MCP bridge communicates through that browser session. Tool results depend on the current document state and on the model's ability to plan motion effectively. LottieFiles notes that animation quality can vary by model and recommends pairing the MCP tools with its motion-design skill for stronger timing and easing decisions. Users should review generated changes before export, especially for accessibility, brand compliance, and complex multi-layer edits. Plan and export limits may also depend on the user's LottieFiles account tier.
Supported Transports
stdio
Command: npx
Args:
-y@lottiefiles/creator-mcp@latest
Frequently Asked Questions
- When should an AI assistant use the LottieFiles Creator MCP server?
- Use it when a workflow needs to create, edit, inspect, or export motion graphics directly in LottieFiles Creator, including UI animations, loaders, branded variants, timing refinements, and reusable Lottie assets.
- What does the LottieFiles Creator MCP server add to an AI assistant's capabilities?
- It gives the assistant live, structured access to the open Creator document and Creator API tools, allowing it to manipulate scenes, layers, shapes, keyframes, colors, timing, imports, and exports instead of only describing how an animation could be built.
- What can an AI assistant access or manage through this server?
- The assistant can work with scene settings, layers, animation properties, shapes, text, transforms, keyframes, easing, fills, strokes, imports, and Lottie JSON exports. It can also inspect the current file and generate variants or suggested fixes for motion and brand consistency.
- How is authentication configured for the LottieFiles Creator MCP server?
- The documented setup does not require an API key or bearer token. The local stdio package connects to the user's active LottieFiles Creator browser tab, and the user must enable MCP from Creator's MCP Settings while keeping the tab open.
- Which transport should be used for the LottieFiles Creator MCP server?
- Use the official local stdio transport launched with npx and the @lottiefiles/creator-mcp package. LottieFiles documents this local bridge for supported MCP clients and does not document a hosted Streamable HTTP or SSE endpoint for Creator MCP.