Connect Lottie Creator to Conductor
LottieFiles' browser-based animation editor. Its local MCP server lets agents build and edit Lottie animations inside the Creator tab you have open.
MCP serverOfficialChecked 2026-11-16
Before you start
- Conductor installed (see its MCP documentation (opens in a new tab)).
- Lottie Creator is available on macOS, Windows and Linux.
- Needs Node.js 18 or later. Open creator.lottiefiles.com and keep the tab open, then turn on Settings → MCP Settings → Enable local MCP and wait for “Local MCP bridge connected”. What you can do follows your Creator workspace and plan.
Step 1: Add Lottie Creator to Conductor
For Claude Code sessions
Saves the server to your Claude Code user settings, so every Conductor workspace gets it.
Terminal claude mcp add --scope user lottie-creator -- npx -y @lottiefiles/creator-mcp@latestFor Codex sessions
Saves the server to
~/.codex/config.toml, which Codex sessions in every workspace read.Terminal codex mcp add lottie-creator -- npx -y @lottiefiles/creator-mcp@latestOr share it with your team
Add this to
.mcp.jsonat the project root and commit it. Claude Code sessions in every workspace on that branch pick it up..mcp.json { "mcpServers": { "lottie-creator": { "type": "stdio", "command": "npx", "args": [ "-y", "@lottiefiles/creator-mcp@latest" ] } } }Or edit Codex's config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.lottie-creator] command = "npx" args = ["-y", "@lottiefiles/creator-mcp@latest"]Good to know- Start a new session in Conductor after adding a server, so the agent loads it.
Step 2: Check it's connected
Terminal claude mcp listIn a Conductor session, click the plug icon in the composer or run
/mcp-statusto see each server's status.Step 3: Try a first request
Ask Conductor something that only works with Lottie Creator connected:
Say to Conductor In Lottie Creator, make a 2-second loading spinner with three dots that bounce in turn.
If it doesn't work
- Conductor has no MCP settings of its own. Claude Code and Codex sessions load the same servers they use outside Conductor.
- Each workspace is a separate git worktree. Servers added with plain
claude mcp addonly apply to the folder you ran it in, so use--scope useror a committed.mcp.json. - Conductor runs on macOS. Environment variables for local servers can go in
.conductor/settings.local.toml, under[environment_variables].






