Repository navigation
MCP: expose scene create/show (not chain — see #884) #885
Description
Split out of #880 (gap 2, first half).
gflow scene create composes ordered/trimmed clips into a Scene and has no MCP twin, so multi-clip assembly from an MCP client means round-tripping media ids through a side channel.
Why this one is a fair port, when chain is not
#880 bundles scene with video chain. They are not the same ask:
scene createcomposes media the user has already paid for. It is free and server-side. That is the same reasoning that madedata downloadnon-exempt in feat: 'gflow data download <media_id>' — a billed asset stranded by exit 7 can only be recovered by paying for it again #865 — an agent whose pipeline needs assembly is stranded exactly as a CLI user would be, and nothing tells it why.video chain/movie runare minutes-long and spend credits per segment. They stay exempt until worker-enqueue lands (MCP: expose video extend, enqueued through the worker #884 / investigate: clamp long MCP operations to the client tool-timeout (or confirm enqueue already covers it) #481).
So this issue covers scene create and scene show only.
Note on the migrated host
concatenate_scene 401s on flow.google.com (see #882, which works around it by downloading a single segment directly). Whatever this tool exposes should be honest about which arm it is on rather than reporting a labs-shaped failure — AGENTS.md § Host-Membership Discipline.
Done when
-
gflow_scene_create/gflow_scene_showregistered insrc/gflow_cli/mcp/tools.py -
"scene create"and"scene show"moved from_MCP_EXEMPTtoCLI_TO_MCP -
docs/MCP.mdupdated - six mirror axes checked, including
create --output - run over a live
serve, separately from the CLI path
Activity
ffroliva commentedon Oct 23, 2026
Measured 2026-10-23 (ffroliva, served flow.google.com):
gflow scene show --scene <id> --project <id>exits 3. The scene routes use the aisandbox REST API, which needs the labs session token. That token is gone for accounts served flow.google.com (#1023), and re-authenticating does not help (#803).So an MCP
gflow_scene_create/gflow_scene_showbuilt today could only be live-verified as the same exit-3 refusal on every account we hold. The issue's "run over a live serve" condition can't be met with a success. I'm holding this until the scene surface is ported to flow.google.com (or a labs-served account is available), rather than shipping a twin whose only observable behaviour is the refusal.ffroliva commentedon Oct 24, 2026
Blocked, so closed until the scene surface is ported. Measured again 2026-10-24 on a profile served flow.google.com:
gflow scene showexits 3, because scenes use the aisandbox REST API and labs.google's session serves no token for any account we hold. An MCPgflow_scene_create/gflow_scene_showcould only return that same refusal, and the live-serve condition above can't be met. Porting scenes to flow.google.com is tracked in #639; reopen this when that lands.