Previz/Developers/Connect a client

    Claude.ai, Claude Desktop and Claude mobile

    by the PREVIZ team

    The custom connector needs PREVIZ's sign-in, which is not open yet. Claude Desktop can connect today through a local bridge that sends your key.

    Before you start

    Partly, todayCredential: API key, through a local bridge (Desktop only)
    Server addresshttps://mcp.aimpreviz.comStreamable HTTP, JSON-RPC 2.0. Your key goes in the Authorization header as a bearer token.

    You need a PREVIZ account and an API key. Mint the key in Account → API keys and give it a monthly credit cap: an agent holding the key can spend inside that cap and no further, and a paid tool answers with a quote and runs nothing until it is called again with that quote's token. The key is shown once; keep it in an environment variable named PVZ_KEY, which the snippets below read.

    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.

    Set it up

    1. 01

      Custom connector (web, desktop, mobile)

      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. The address to paste is https://mcp.aimpreviz.com. A connector added on the web follows you to the desktop and mobile apps.

    2. 02

      Claude Desktop today: a local bridge

      Claude Desktop also runs local servers from its config file. The community mcp-remote bridge runs on your machine, talks to PREVIZ over HTTPS and sends your key as a header. It needs Node.js installed. Edit the config from Settings → Developer → Edit Config, then restart Claude Desktop.

      claude_desktop_config.json
      {
        "mcpServers": {
          "previz": {
            "command": "npx",
            "args": [
              "-y",
              "mcp-remote",
              "https://mcp.aimpreviz.com",
              "--header",
              "Authorization:${PVZ_AUTH}"
            ],
            "env": {
              "PVZ_AUTH": "Bearer pvz_YOUR_KEY"
            }
          }
        }
      }
    3. 03

      Check it

      Open a new chat; PREVIZ's tools appear under the tools menu. Ask Claude to list your PREVIZ projects.

    Config formats belong to each client and change with its releases; if a field name above is refused, check the client's own documentation for its current remote-server entry. The address and the header never change.

    Test the connection

    Two free calls prove the whole path: the key, the address, the client and your projects. Neither spends a credit.

    1. Ask for your PREVIZ projects. The client calls list_projects and answers with their names and ids. An empty list means the key reaches no project yet, not that the connection failed.
    2. Ask what a cinematic frame of something would cost in one of them. The client calls plan_quote or generate_frame without a quote token, and answers with a price. Nothing renders and nothing is charged.
    3. If the client reports 401 or unauthorized, the key is missing, mistyped or revoked; if it reports no tools, the address or the transport is wrong. Fix that before anything else.

    What to know

    • The web and mobile apps cannot send a key header, so until PREVIZ's sign-in opens they cannot connect.
    • The local bridge is not a PREVIZ product; it is a widely used community package. Keep its config file private: it holds your key.
    • Listing in Claude's connector directory is not something PREVIZ offers.