Connect your own AI
Use the AI assistant you already have open to make and edit animations with Mosso. The local connector runs on your computer and exports Lottie, dotLottie, animated SVG or Mosso project files.
Use mosso-mcp with Claude Desktop, Claude Code or Cursor. The connector runs on your computer and uses your own AI account.
What you need
- Claude Desktop, Claude Code or Cursor. MCP means Model Context Protocol.
- Node.js 20 or later, including npm.
- A folder where you can save exports. The examples below use
~/Mosso.
These steps use mosso-mcp@0.1.0. The first run downloads the package from npm. Use your own AI account.
Claude Desktop
Open Settings > Developer > Edit Config.
Add this one-line config to the file that opens. Keep any servers you've already added:
{"mcpServers":{"mosso":{"command":"npx","args":["-y","mosso-mcp@0.1.0","--output-dir","~/Mosso"]}}}Quit Claude Desktop completely and reopen it. Check that Mosso appears in the tools menu.
On Windows, use C:/Users/your-name/Mosso for the output folder. If Windows can't find npx, use "command":"cmd" and start the args with "/c","npx".
Claude Code
Run this one-line command in your terminal:
claude mcp add --scope user --transport stdio mosso -- npx -y mosso-mcp@0.1.0 --output-dir ~/Mosso
Run claude mcp list to check the connection. Use /mcp inside Claude Code to see Mosso's status. On Windows, put cmd /c before npx.
Cursor
Open Settings > Tools & MCP > Add new global MCP server. Add this one-line config to ~/.cursor/mcp.json, keeping any existing servers:
{"mcpServers":{"mosso":{"command":"npx","args":["-y","mosso-mcp@0.1.0","--output-dir","~/Mosso"]}}}For one project, use .cursor/mcp.json in that project instead. Check Mosso's status under Tools & MCP, then enable it for Agent. On Windows, use the folder and cmd settings shown above.
How to sign in
The local connector has no sign-in step. To keep editing in the web app, ask your assistant to export a Mosso project file. Open Mosso's sign-in page, then use Google or the email code sent to your inbox. Drop your project file on the projects page, then open it in the editor.
If Mosso doesn't connect
Run npx -y mosso-mcp@0.1.0 --version in your terminal. It should print 0.1.0. If npx is missing, reinstall Node.js and restart your assistant. If it works in your terminal only, use the full path to npx in your config.
What to ask
- "Make a loading spinner in #3a5bff and #16c2a3 and save it as a Lottie file."
- "Find a confetti animation and make it in our brand colours. Save it as dotLottie."
- "Make a launch post for Instagram that says Version 2 is here, with a calm feel."
- "Make the success check slower, loop it, and export it as an animated SVG."
- "Make a 9:16 version of it and save both files."
What the assistant can do
| Tool | What it does |
|---|---|
search_library | Finds library items by words and kind: loaders, celebrations, text, logo reveals, posts, icons and more. |
create_animation | Builds an item, or a blank canvas, in your colours, fonts and motion style, with your words. |
describe_animation | Lists the layers with their timing, text and colours, in plain text. |
edit_animation | Changes it with the same edits Mosso's own AI uses. A failed edit call leaves that call's document unchanged. Earlier successful calls stay applied. |
export_animation | Saves Lottie JSON, dotLottie, animated SVG or a Mosso project file. |
list_animations | Lists what it made in this session. |
Where the files go
On your computer, Mosso only ever writes inside the one output folder, and never replaces a file unless the assistant asks it to. Exports contain no expressions. Save your work before closing the assistant: animations stay in memory until you export them. MP4, GIF and WebM need a browser to draw every frame: export a Mosso project file, open it in Mosso and export the video from there.
Something missing or wrong here? Write to hello@mosso.video.
Try these animations
Open an example to try its colours and timing, or edit it in Mosso.