First video

After Fluos is connected, send a brief and follow the create → poll → export workflow.

Read the skill at fluos://skill (the Video MCP serves it on resources/read). Then send a first job. Fluos creates and renders the video — your agent briefs it and collects the result. Do not call dashboard chat.

First-job prompt

Use Fluos as the video crew for this task. List my workspaces and projects, create a project if needed, then make a 15-second 9:16 launch teaser with a bold opening hook, kinetic product headline, and clear CTA endcard. Poll get_status until the preview is ready, then share the preview with me. Let Fluos do the video work; do not try to build or render video locally.

Workflow

  1. list_workspaces → list_projects or create_project
  2. list_assets / upload_asset if the brief needs footage or a reference
  3. create_video with a brief (optional recipe and format)
  4. Poll get_status every 5–8 seconds until ready or failed
  5. revise_video to iterate, or export_video → get_export for a file

One running job per project — if you get JOB_STILL_RUNNING, poll or cancel_job.

create_video succeeding with a jobId is expected. Failures appear later on get_status as failed, not as MCP protocol errors. See Errors.

What to pass on create_video

{
  projectId: string;
  brief: string;
  recipe?: "generate" | "edit" | "compose" | "mix";
  assetIds?: string[];
  format?: {
    aspectRatio?: string;
    durationHintSeconds?: number;
    resolution?: string;
  };
}

If you omit recipe, Fluos classifies from the brief and attached assets. See Recipes.

Uploads

upload_asset is two-step. The first call returns uploadUrl. POST the bytes, then call again with storageId. Optional filename, mediaType, and size. Do not send raw video bytes in the JSON-RPC body.

If you get ASSET_NOT_READY, wait and retry create_video.

Export

export_video queues a render in mp4, gif, webm, mov, or png-sequence (format optional, default mp4). Poll get_export until the file is ready.

Ready exports return a signed playbackUrl. Hosts that support MCP Apps also get an inline player. If the player does not render, open playbackUrl.

Where the work lives

Jobs write into the same workspaces, projects, library, and exports as the website. Open the project in the dashboard to preview or keep editing in chat.

Need the full tool list? See Tools.