Connect LottieFiles to Conductor
Platform for Lottie animations. Its hosted MCP server gives agents your LottieFiles workspace through a small GraphQL toolset, acting with your account's permissions.
MCP serverOfficialChecked 2026-11-16
Before you start
- Conductor installed (see its MCP documentation (opens in a new tab)).
- LottieFiles is available on macOS, Windows, Linux and the web.
- Needs a LottieFiles account; your agent opens a sign-in page the first time it connects. The four tools explore and run LottieFiles' GraphQL API rather than one tool per action.
Step 1: Add LottieFiles 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 --transport http lottiefiles https://mcp.lottiefiles.com/mcpFor Codex sessions
Saves the server to
~/.codex/config.toml, which Codex sessions in every workspace read.Terminal codex mcp add lottiefiles --url https://mcp.lottiefiles.com/mcpOr 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": { "lottiefiles": { "type": "http", "url": "https://mcp.lottiefiles.com/mcp" } } }Or edit Codex's config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.lottiefiles] url = "https://mcp.lottiefiles.com/mcp"Good to know- Start a new session in Conductor after adding a server, so the agent loads it.
- To sign in, open Conductor's MCP status dialog and use the sign-in action on the server's row.
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 LottieFiles connected:
Say to Conductor List the Lottie animations in my LottieFiles workspace and tell me which ones were updated most recently.
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].






