publish_scene

io.github.streamloop/mcp · Verify this server

Publishes the draft exactly as it was at draftRevision (required) as the scene's next version: what streams playing it play from then on. All of it is checked first; a refusal (SCENE_INVALID) lists each problem — fix them with scene_set and publish again. Edits made after draftRevision are not published (the answer says so, stale: true). If someone published after the version your draft is based on, it is refused (STALE_PUBLISH: publishedVersion and what would be reverted) — read the draft again; only with the user's say-so send overwritePublished: <that version>. When that version is a revert (publishedVersionIsRevert), reading again changes nothing: overwritePublished, or discard_scene_draft to keep it.A scene on air is refused with CONFIRM_REQUIRED naming the streams — tell the user, then send confirm: true. An unchanged draft publishes nothing; dryRun checks it and lists what would change. Answers summary (what happened and what to do next), version, publishedAt, changes (what changed, as resource paths), notes, and the streams playing it.