Use the MCP sequence Studio expects so each request keeps its Project, Pipe, media, and approval details attached.
Before you start #
Connect the client, choose the intended Project access, and keep Studio open so approvals and job status remain visible.
Generate from current context #
- Read
context.get. - Choose exactly one origin: current context, regenerate, Use in Pipe, or mapped sources.
- Clone context for edits or variants.
- Submit the prepared context.
- Show the Studio approval or job status.
This sequence keeps the visible workspace connected to the generation the agent submits.
Reuse project media #
- Inspect the project and folder context.
- Choose the source image or clip explicitly.
- Map it into a compatible Pipe field.
- Clone only when values must change.
- Submit and report the save location and job status.
Set up an imported Pipe #
Use this tool sequence:
pipe.inspect
dependencies.inspect
pipe.setup- Read every
pipe.inspectpage throughhas_more=false. - Run
dependencies.inspect. - Stage the complete
pipe.setupproposal. - Show the approval and stop.
The proposal may rename the Pipe, label nodes and fields, choose visibility, group Core and Expanded controls, reorder every graph node, and add or toggle standard bypass controls including bypassed-by-default. It preserves ordinary workflow values, defaults, and graph inputs, and the Pipe keeps exactly one terminal output. Missing dependencies are reported separately; pipe.setup never installs them. Dependency installation requires Build & configure.
Studio validates and stages the proposal. Approval and run apply it. The agent must show the approval and stop. If the Pipe revision changes after inspection, re-inspect every page and prepare a fresh proposal.
Recover output #
When a job finishes but the expected image or clip is missing, inspect the job and delivery status before submitting again. Confirm the final workflow output, Project folder, and media type. Another generation will not fix an unknown save or transfer problem.