Same credits, same generations, from your agent.
The MCP server is a thin layer over the same Loovie generation pipeline the mobile app uses, so credit costs match the app exactly. Estimates come from the same estimator, jobs run on the same workers, results land in the same project. During beta we are actively fixing rough edges, so expect occasional weirdness in less-tested clients. File an issue, we will get to it.
Officially supported, plus everything else.
Four clients we test on every release. Everything else that speaks Streamable HTTP MCP should work, and if it does not we want to know. No SLA during beta, just a Discord and a GitHub issues tab.
Officially supported
- Cursor One-click install. Tested on every release.
- Claude Code Plugin marketplace install. Skills and slash commands included.
- Claude Desktop One-click via the .dxt bundle, or Settings → Connectors → Add custom connector.
- Claude.ai (web) Connect as a custom MCP integration.
Compatible, community-supported
- VS Code Copilot Chat Add to .vscode/mcp.json or user settings.
- Continue Add under mcpServers in config.json.
- Cline Add under mcpServers in cline_mcp_settings.json.
- OpenCode Add under mcp in opencode.json.
- Any Streamable HTTP MCP client Point it at the endpoint, finish OAuth, done.
Three paths. Pick one.
The launcher writes the right config for the right client. If you prefer to wire things yourself, the snippets are in the docs.
One command
Detects your client, writes the config, kicks off the OAuth flow.
npx -y @loovie/mcpClaude Code
Two commands. Adds the marketplace, then installs the plugin with skills and slash commands.
claude plugin marketplace add looviehq/loovie-communityclaude plugin install loovie-mcp@loovieMore clients (VS Code, Continue, Cline, OpenCode)
{
"mcpServers": {
"loovie": { "url": "https://api.loovie.app/v1/mcp" }
}
}{
"servers": {
"loovie": { "url": "https://api.loovie.app/v1/mcp" }
}
}{
"mcpServers": {
"loovie": { "url": "https://api.loovie.app/v1/mcp" }
}
}{
"mcpServers": {
"loovie": { "url": "https://api.loovie.app/v1/mcp" }
}
}{
"mcp": {
"loovie": { "type": "remote", "url": "https://api.loovie.app/v1/mcp" }
}
}
Any client that speaks Streamable HTTP MCP can point at https://api.loovie.app/v1/mcp and finish OAuth in the browser.
The creative core of Loovie, from your prompt.
The MCP server exposes the same generation and editing tools the app builds on. Story-mode flows, sketches, and a handful of editor-only surfaces aren\'t in MCP yet, those still live in the mobile app for now. The agent picks what to call, you approve the spend, the result lands in your project.
Characters
Create from a photo or a prompt, generate optional reference sheets, manage variations, clone and edit.
Generation
Image, video, first and last frame, character swap, motion control, AI VFX. Each spend tool quotes credits before it runs.
Editing
Clips, trims, splits, captions, picture-in-picture, transitions, music tracks, volume, color and effects.
Library
Browse and search music, SFX, style presets, starter characters, and backgrounds. Drop tracks and SFX into your project, clone starter characters into your library.
Install, sign in, talk, approve.
Install
One command (npx -y @loovie/mcp), one-click in Cursor, or two lines in Claude Code. The launcher writes the config for you.
Sign in
A browser tab opens for OAuth. Approve once, your client stores the token and reuses it across sessions.
Talk to your agent
Ask for what you want: "make a 15s ad of a robot drinking coffee", "swap the character in clip 3", "add captions to the last scene".
Approve, then watch
The agent estimates credits, asks you to approve, runs the job, and surfaces the result (inline in clients that render markdown images, as a clickable URL everywhere else). Set an auto-approve threshold once and small spends just go.
What you'll see in each client.
Tools return both signed media URLs and resource attachments, so clients with markdown image support show previews inline. Everything else falls back to a clickable link.
| CLIENT | MEDIA RENDERING |
|---|---|
| Cursor | Inline image previews, video links open in your browser. |
| Claude Code (CLI) | Clickable URLs (cmd+click in iTerm2, ctrl+click elsewhere). Terminals don't render images inline yet. |
| Claude Desktop | Inline image previews. Videos open externally. |
| Claude.ai (web) | Image thumbnails inline, signed URLs for videos. |
| VS Code Copilot Chat | Markdown image rendering, links for video. |
| Continue / Cline / OpenCode | Markdown rendering varies by client. URLs always work. |
Sandboxed clients need api.loovie.app on the allowlist.
Claude.ai on the web and Claude Desktop run tools inside a sandbox
with a network allowlist. Add api.loovie.app
under Settings, then Connectors, then allowed domains or network
access. This is what lets the agent fetch your generated assets, so
image previews render inline, and it is also required for any
image-to-image edit that needs to read an existing asset.
Without it, a preview can show up blank, or an edit can fail to load its source image. Terminal clients like Claude Code are not sandboxed and need no allowlist changes.
Credits, quoted up front. Approvals, on your terms.
Every spend tool has a matching estimate_* that quotes
the credit cost before anything runs. The execute_* tool
then waits for your approval, charges, and runs the job. Estimate
equals charge equals render, no surprises.
Set an auto-approve-below threshold once and small spends just go.
Larger jobs always prompt. Your account balance is one
get_credit_balance call away.
Skills and slash commands.
The plugin ships opinionated skills and slash commands for the most common flows. Other clients get the raw tools and resources directly.
Skills
- making-a-loovie-video
- character-from-photo
- editing-an-existing-project
- exporting-and-sharing
Slash commands
- /loovie-new-project
- /loovie-status
- /loovie-credits
Skills and slash commands are a Claude Code feature. Cursor, Claude Desktop, and other MCP clients still get every tool and resource, just without the opinionated wrappers.
Open source, Apache-2.0.
The launcher, the plugin, the skills, the slash commands, the docs: all of it lives in the public loovie-community monorepo. Fork it, file issues, send PRs. Read the source before you install it, that is the point.
Ready to drive Loovie from your agent?
One command in your terminal, one click in Cursor, or two lines in Claude Code. You will need a Loovie account, sign in once and the launcher remembers you.