Previz/Developers

    PREVIZ for programs

    by the PREVIZ team

    One MCP server at https://mcp.aimpreviz.com. Your agent or script acts as you, on your projects, through the same gated, metered functions the studio's buttons run.

    The address

    Every client, every script and every recipe on these pages talks to this one address. Nothing else serves the door, and no client needs anything installed from PREVIZ.

    Server addresshttps://mcp.aimpreviz.comStreamable HTTP, JSON-RPC 2.0. Your key goes in the Authorization header as a bearer token.

    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. A key holds only the access classes its owner gave it, set in Account → API keys → the key's Access: a new key holds read and write, and spend needs a monthly credit cap. tools/list shows only the tools a key holds, and a call to any other is refused with INSUFFICIENT_SCOPE. A key made before access classes existed keeps what it could do then (read, write, spend and live) until its owner sets its access; produce is given, never inherited.

    Server PREVIZ 0.28.0 · protocol versions 2025-11-25 and 2025-06-18 · 102 tools.

    Quickstart

    Five steps from no key to a first render, with nothing spent until the last one.

    1. 01

      Mint a key

      Account → API keys. Give it a name and a monthly credit cap. It is shown once; keep it in an environment variable.

    2. 02

      Connect a client

      Pick your client below. Every recipe sends the key as a bearer header to the same address.

    3. 03

      Read first

      Ask for list_projects, then get_board on one of them. Reads are free and change nothing.

    4. 04

      Price before you spend

      plan_quote prices a whole plan and reports anything the project's engine policy would refuse. Still free.

    5. 05

      Spend on purpose

      Call a paid tool and it answers with its quote and a quoteToken, and runs nothing. Send it again with that token, or with your own idempotencyKey, and it renders once, inside the key's cap; a retry joins the same run and the work is charged once.

    Your first call: list the projects this key can reach
    curl -s https://mcp.aimpreviz.com \
      -H "Authorization: Bearer $PVZ_KEY" \
      -H "Content-Type: application/json" \
      -H "Accept: application/json, text/event-stream" \
      -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
           "params":{"name":"list_projects","arguments":{}}}'

    Connect a client

    One recipe per client: the config, how to check it worked, and what it cannot do. A client marked Not yet is not a promise of a date.

    Claude

    OpenAI

    Editors

    • Cursor
      Works today

      Works today with an API key in a header.

    • Works today with an API key in a header.

    • Windsurf
      Works today

      Works today with an API key in a header.

    • Cline
      Works today

      Works today with an API key in a header.

    • Zed
      Works today

      Works today with an API key in a header.

    Terminals

    Frameworks

    Automation

    • n8n and Make
      Partly, today

      Works today over MCP with a key header; a REST mapping is not built yet, so a plain HTTP step sends JSON-RPC.

    Direct

    Concepts

    The five ideas the reference assumes you have.

    • Auth and keys

      How a program proves who it is to the PREVIZ door: a personal API key in a header today, what that key can reach, and how to bound it.

    • Quotes and money

      How a paid PREVIZ tool answers with a quote and spends nothing, how its quote token or your own idempotency key turns it into exactly one charge, and what an agent can and cannot buy.

    • Projects and engine policy

      Why every PREVIZ call names a project, and how that project's engine policy decides which engines may touch the work before a credit moves.

    • Continuity

      How PREVIZ holds a cast, a prop or a location faithful across every frame an agent renders, how a program reads the project's memory and its decisions, and how it re-shoots exactly what a changed decision made stale.

    • Jobs and events

      Which PREVIZ tools answer at once and which start work that lands later, how to poll for it, and how one cursor watches every project.

    Tool reference

    All 102 tools, by what they do. Each page gives its arguments, its answer, its access class, its live price and how it fails.

    Shoot

    Frames, edits, takes, frame surgery and meshes, through the same gated, metered functions the studio's own buttons run. A paid one called without a quoteToken or an idempotencyKey answers with its quote and runs nothing.

    Board

    Place results on an Infinitum board, lock an identity, pin a note. Free writes to your own projects.

    Cut

    Read a Sequence Lane as a conform manifest and render the cut.

    Live

    Read a live session's direction log, direct a set that is on air, play a board live.

    The whole reference on one page, with every error the door returns

    Not built yet

    Said plainly so nobody builds against something that is not there. Each moves into the pages above when it ships, and not before.

    • A PREVIZ REST mapping of the same operations is not built yet; every call is JSON-RPC to the MCP server.
    • Webhook delivery is not built yet; poll the events_since tool for finished takes, meshes and drift warnings.
    • A PREVIZ client package of its own is not built yet; any MCP client, or plain HTTPS, works today.
    • Cancelling a running job is not built yet; get_job waits for and reads a job, and its receipt says what it charged.
    • Sign-in from clients that take only an address (Claude.ai's connector, ChatGPT) is not open yet; use a client that can send a header.