n8n and Make
by the PREVIZ team
Works today over MCP with a key header; a REST mapping is not built yet, so a plain HTTP step sends JSON-RPC.
Before you start
https://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
- 01
n8n: the MCP Client Tool node
Inside an agent workflow, add the MCP Client Tool node. Set the endpoint to https://mcp.aimpreviz.com, the transport to HTTP Streamable, and authentication to Header Auth with the name Authorization and the value "Bearer" followed by your key. The agent node then sees PREVIZ's tools.
- 02
Make, or a fixed n8n step: one HTTPS request
For a step that always does the same thing, send one JSON-RPC request with an HTTP module or node: POST, the headers below, and the body naming the tool. The answer's result.structuredContent holds the fields.
RequestPOST https://mcp.aimpreviz.com Authorization: Bearer pvz_YOUR_KEY Content-Type: application/json Accept: application/json, text/event-stream {"jsonrpc":"2.0","id":1,"method":"tools/call", "params":{"name":"list_projects","arguments":{}}}
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.
- 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.
- 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.
- 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
- A paid tool sent without a quoteToken or an idempotencyKey returns a quote and runs nothing; a scenario that spends sends the quote request first, checks it, then sends a second request carrying the quote's quoteToken, or sends its own idempotencyKey from the start.
- A request that carries a quoteToken or an idempotencyKey is one run however often the HTTP node or module retries it: a retry joins the first run and is charged once. A render that outlives the wait answers a jobId; poll get_job with it rather than resending.
Then
Once the test passes, the reference and the concepts are where the work is.