PREVIZ for programs
One server, the Model Context Protocol over HTTPS. Your agent or script acts as you, on your projects, through the same gated, metered lanes as the studio.
Coming next: Claude.ai and Claude Desktop, which add a server from its address alone. You will add PREVIZ as a custom connector and approve it on a PREVIZ sign-in page — no key to paste. Until that opens, use a client that can send a key.
What a program can do today
The server's tools, grouped. Reads are free; anything that renders quotes first. Your program acts as you, on the projects you own, under each project's engine policy.
Read a project like a director
List your projects, summarise a board, filter its frames by lane, locked identity, look or recorded drift verdict, and walk its lineage as a graph. Free, exact, nothing inferred.
Continuity locks
Read and lock the characters, objects and locations a project holds faithful. A lock rides into a render by name, and a recorded drift verdict can be read back per frame.
Frames, takes and meshes
Render a frame in a named look, animate a take from it, or build a 3D mesh, through the same gated, metered lanes the studio's own buttons run.
Quote before spend
Every paid tool answers with its price and runs nothing until it is called again with your own idempotency key (or the quote's token). A retry with the same key is the same run, charged once. A whole plan can be priced and checked against the project's engine policy first.
Frame surgery
Depth maps, layer splits, inpainting, relighting and a clean-plate split for compositing, each through the lane the canvas uses.
Cuts, events and the live set
Read a Sequence Lane as a conform manifest, render the cut, poll a cursor for finished takes, jobs and drift warnings (none skipped, even two in the same millisecond), and write direction into a live session.
How to call it
Add the server to an MCP client with one line, or call it over HTTPS yourself. Mint a key in Account → API keys; it is shown once.
claude mcp add --transport http previz \
https://mcp.aimpreviz.com \
--header "Authorization: Bearer pvz_YOUR_KEY"# Price a frame before anything runs (no credits move).
# YOUR_PROJECT_ID is an id from the list_projects tool.
curl -s https://mcp.aimpreviz.com \
-H "Authorization: Bearer $PVZ_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0", "id": 1, "method": "tools/call",
"params": {
"name": "plan_quote",
"arguments": {
"projectId": "YOUR_PROJECT_ID",
"steps": [
{ "tool": "generate_frame", "args": { "prompt": "rain on a neon street", "tier": "cinematic" } }
]
}
}
}'
# The answer: credits per step, the total, and whether the project's
# engine policy would refuse any step. Nothing was rendered or charged.# The same tool with no idempotencyKey returns a quote and runs nothing.
# Send your own idempotencyKey to spend and render. The same key retried
# after a dropped connection joins the same run and is charged once; the
# same key with different arguments is refused.
{
"name": "generate_frame",
"arguments": {
"projectId": "YOUR_PROJECT_ID",
"prompt": "rain on a neon street",
"look": "Film Noir",
"idempotencyKey": "shot-14-take-1"
}
}
# A quote that carries a quoteToken can be run by sending that token
# instead: exactly what was quoted, at that price, inside ten minutes.
# "confirm": true still runs for API keys until 4 Dec 2026, but every
# retry of it is a new charge, and it is never accepted for a sign-in.Where it fits
Your own agent
Any client that speaks MCP holds PREVIZ as tools: read the board, plan a sequence, price it, then render under the project's own engine policy and continuity locks.
Edit bay and 3D
The panels for the two edit-bay applications and the add-on for the 3D application use this same server: conform a cut into a timeline, or import a mesh with its provenance stamped on it.
Pipeline scripts
A script can call the server directly over HTTPS: pull the cut manifest into an edit, the provenance report into a tracker, and finished takes from the events cursor.
What the tools return
Frames made in PREVIZ. A render returns the file, where it landed, and what it cost.
Not built yet
Said plainly so nobody builds against something that is not there. Each moves to the list above when it ships, and not before.
- A PREVIZ REST mapping of the same operations is not built yet; today every call is JSON-RPC to the MCP server.
- Official client libraries are not built yet; any MCP client, or plain HTTPS, works today.