For agents

Give your agent a film crew.

Crewcut speaks MCP and plain HTTP. Your agent names a topic and gets back a finished video, a Short, a thumbnail and the upload package. You stay the one who says yes.

What an agent can do

  1. 01

    Start a video

    One call with a topic. It may also pick a look, a voice and a layout. It gets a job id back at once.

  2. 02

    Follow the shoot

    Ten stages, each reporting its state. If one fails, the error says why, and resume picks up at that stage.

  3. 03

    Read the result

    The package (title, description, chapters, tags), plus paths to the video, the Short, the thumbnails, the QA report and the fact check.

  4. 04

    Bring it to you

    It shows you the cut and waits. Approve and reject are tools too, but they record your decision. They do not publish.

MCP server

The server runs over stdio with the command rwv mcp. Add it to any MCP host (Claude Desktop, Claude Code, Cursor and others) with this entry:

MCP config
{
  "mcpServers": {
    "crewcut": {
      "command": "rwv",
      "args": [
        "mcp"
      ],
      "env": {
        "WORKDIR": "./jobs"
      }
    }
  }
}

WORKDIR is where jobs and their files go. The server appears to the agent as crewcut.

ToolArgumentsWhat it does
create_videotopic, theme?, voice?, layout?, mode?Starts a job. Returns a job id straight away; the crew works in the background.
list_videosnoneEvery job in the workspace with its state.
get_statusjob_idThe current stage, the state of all ten stages and any error, as JSON.
get_packagejob_idTitle, description, chapters and tags, ready to paste into YouTube.
get_artifactsjob_idPaths to the video, the Short, the thumbnails, the QA report and the fact check.
resumejob_idPicks a stopped job up at the stage that failed. Finished stages are not redone.
approvejob_idRecords the owner's yes. It uploads nothing by itself.
rejectjob_id, noteSends the cut back with a note.

Optional arguments: theme is one of brand, classic, paper; voice is one of bill, sarah, george, jessica; layout is one of stage, center, clean, split; mode is graphics (every shot drawn in code, the default) or trailers.

HTTP API

rwv serve starts the API on 127.0.0.1:8787. Set RWV_API_TOKEN and every request must carry it as a bearer token. The OpenAPI description is served at /openapi.json, and a copy lives at /openapi.json on this site.

Start a video
curl -s -X POST http://127.0.0.1:8787/api/jobs \
  -H "Authorization: Bearer $RWV_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"topic": "Best budget espresso machines, ranked"}'
Check on it
curl -s http://127.0.0.1:8787/api/jobs/<id>/status \
  -H "Authorization: Bearer $RWV_API_TOKEN"
EndpointBodyWhat it does
GET /api/healthnoneIs the engine up, and which keys does it have.
GET /api/jobsnoneEvery job with its state.
POST /api/jobs{ "topic": "..." }Start a job. Returns its id.
GET /api/jobs/{id}/statusnoneStage, state and output paths.
GET /api/jobs/{id}/events?since=NnoneThe event log from index N: stage starts, log lines, artifacts.
GET /api/jobs/{id}/runnoneThe run summary. Fields fill in as stages finish.
GET /api/jobs/{id}/files/{path}noneAny file the job made: video, Short, thumbnail, package.
POST /api/jobs/{id}/resumenoneResume a stopped job.
POST /api/jobs/{id}/decision{ "decision": "approve" }Approve or reject. Records the decision only.
POST /api/jobs/{id}/upload{ "confirm": true }Private upload. Refused unless the job was approved first.

A prompt to paste

Once the server is connected, this is enough to get a first video and keep yourself in the loop:

Say this to your agent
Use the crewcut tools. Call create_video with the topic I give you, poll get_status until it is done, then show me get_package and wait for my yes before you call approve. Never upload anything yourself.

Rules that hold for agents

  • You approve. An agent can call approve only if you gave it that permission. Without it, the job waits for you.
  • Uploads are private. There is no argument, flag or setting that makes an upload public or unlisted. A person publishes on YouTube.
  • Approval comes first. The upload endpoint refuses a job that has not been approved, and it needs an explicit confirm.
  • The content rules still apply. No em or en dashes, six minutes at most, your own products disclosed, rankings honest, every claim checked against a source. A job that breaks one stops and says which.

Keys

On your own machine the engine reads ANTHROPIC_API_KEY and ELEVENLABS_API_KEY from the environment, so an agent-run job is a bring-your-own-keys job: the providers bill you, and the job's cost file lists every call. Keys are read from the environment only. They are never written to a log, an event or a file the agent can read back.

What runs today

The engine, the MCP server and the API run locally today, for anyone with the repository. The hosted endpoint for subscribers opens together with checkout. Until then there is no hosted API, and nothing on this page should be read as one.

See the plans