Short answerThe MCP server exposes the pipeline itself — runs, the bible, episode scripts, the world pack, art and renders, covers, sign-off, the delivery package and your credit balance — as tools that map one-to-one onto what the console does. Approval gates stay yours; the agent hands you a console link at each one. Visual review, fixing shots and publishing remain console work.
Each tool is a thin proxy for the same server-side action the console triggers; validation, gates and pricing are identical.
| Stage | Tools | Notes |
|---|---|---|
| Runs | list_runs, get_run, create_run, delete_run | create_run needs a premise (100–6,000 characters), a title in the primary language and compliance_ack: true. Episode count is fixed at 10 for self-serve accounts. |
| Bible (step 2) | generate_bible, get_bible, update_bible, sync_bible, approve_bible | generate_bible accepts feedback for a rewrite. get_bible reports stale_eps when beats lag behind the scripts. |
| Scripts (step 3) | generate_scripts, get_script, update_script, approve_script | generate_scripts resumes by default and skips finished episodes; force: true rewrites the whole chain. Episode numbers look like 0001. |
| World pack (step 4) | generate_pack, update_pack, commit_pack | Committing the pack creates the episodes and opens art and rendering. |
| Art & render (step 5) | art_estimate, generate_art, art_status | generate_art spends credits; run art_estimate first and confirm with the user. |
| Covers | covers_estimate, generate_covers, set_cover_theme, regen_cover | Cover generation is priced per image; the estimate lists which episodes lack one. |
| Finishing | signoff_episode, build_delivery_pack | Sign-off is a human decision: the agent should only call it after you have watched the episode. The delivery package is built only when you ask. |
| Account | credits_balance, get_review_url | get_review_url makes no API call; it returns the console deep link for the run. |
Two tools, import_clip and upload_character_ref, are reserved for Dawnwood staff and return an error on customer accounts.
Three actions change what the pipeline is allowed to do next: approve_bible, approve_script and commit_pack. Well-behaved agents call get_review_url before each of them and stop. Open the link, read the bible or script in the console, and either approve there or tell the agent to approve. Rendering starts only after the pack is committed, so nothing burns credits that a human did not clear. Sign-off works the same way: the agent may call signoff_episode, but only after you have seen the episode master.
If you ask the agent to approve without reviewing, it will comply — the gate is a workflow convention, not a lock. Keep the review step if you want the safety.
Bible generation, the script chain, art and covers run in the background. The agent tracks them by polling:
get_run for the wizard steps, art_status for art and rendering, covers_estimate for covers.list_runs is for browsing, not polling. It is expensive and returns every run.The tool descriptions carry these rules, so most agents follow them without being told.
The same price card as the console applies; see what costs credits. Over MCP the spending tools are generate_art (art and renders), generate_covers and regen_cover (covers), and script edits made after an episode is approved. Bible and script generation before approval are free, which means a Free account can take a premise through the full bible and every script without spending anything. Failed generations are not charged.
Every charge is tagged with the token that made it. API tokens in the console shows credits spent per token, and credits_balance returns a breakdown by source (console versus each agent name) and by token.
Every run, version and charge an agent creates appears in the console exactly as if you had clicked it. The bible and script pages keep version history with the actor recorded, the Credits page itemises spending by source, and Where is my history in the console answers the rest; see where is my history.
Still stuck? Email support@dawnwood.ai with your account email, the series, the episode and the segment or group — see what to include.