Bring your own agent
Drive Sundream from Claude Code, Codex, or any agent that speaks MCP — the same tools the built-in agent uses.
Sundream's studio tools are available over MCP, so an agent you already use can plan a film, build its storyboard, and start renders. It drives the same tools the built-in agent does, against the same projects — work done by your agent shows up in the studio, and work done in the studio is visible to your agent.
Your agent brings its own model, so the writing and planning cost you nothing here. Credits are only spent on generations.
Two ways to connect
| Local | Remote | |
|---|---|---|
| Run | npx @zeta-studio/mcp on your machine | Connect to our hosted endpoint |
| Best for | Claude Code, Codex, Cursor — anything on your desktop | Agents that connect to hosted MCP servers |
| Media | Can mirror finished renders into a local folder | Stays hosted; tools return URLs |
The local package is the one to start with. It's the only way to get finished clips onto your own disk — a hosted server can hand back a URL, but it can't write a file onto your machine.
What your agent can do
Everything the built-in agent can, minus the parts that only make sense in a browser. It can create and duplicate projects, write scenes and dialogue, add cast and locations, choose models, render portraits, frames and clips, assemble a timeline, and export the film.
It can also hold several projects at once — every tool takes an explicit project id, so an agent can draft two variations side by side, or duplicate a finished film and try a different look in the copy.
Renders still need a decision
An agent spending your credits without asking is the failure mode worth designing against, so every key carries a spend policy: either each render is quoted and waits for approval, or renders run freely up to a cap you set.