ViewMax MCP Server for Claude, Cursor and Codex
ViewMax MCP puts video generation inside the assistant you already have open. Add the ViewMax MCP server to Claude, Claude Code, Cursor or Codex, describe the shot in the chat you are already in, and get a finished clip back as a link.
What ViewMax MCP is
MCP, the Model Context Protocol, is the standard an assistant uses to reach a tool that lives somewhere else. ViewMax MCP is the ViewMax Studio implementation of it: a hosted server that exposes video generation as four ordinary tools, so the model can call them the same way it calls its own file reader or web search.
The ViewMax MCP server runs on our side, not yours. There is no package to install, no local process to keep alive and no configuration beyond a URL and a key. It speaks Streamable HTTP and is stateless, so every request carries its own credentials and is answered on the spot. Protocol versions 2025-06-18, 2025-03-26 and 2024-11-05 are all accepted, which covers every current client.
A render booked through ViewMax MCP is the same render the website books. Same models, same credit prices, same account, same history page afterwards. The ViewMax MCP server is a second door onto the room, not a separate product with its own rules.
| Server URL | https://viewmaxstudio.net/api/mcp |
|---|---|
| Transport | Streamable HTTP, stateless. No local process. |
| Authentication | ViewMax Studio API key, sent as Authorization: Bearer or x-api-key. |
| Protocol versions | 2025-06-18, 2025-03-26, 2024-11-05. |
| Tools | generate_video, get_video, get_credit_balance, list_video_models. |
| Clients | Claude, Claude Desktop, Claude Code, Cursor, Codex, and any other MCP client. |
| Rate limit | 60 requests a minute per key. |
| Render time | Two to four minutes a clip, depending on the model. |
| Billing | ViewMax Studio credits, at the same per-second rates the website charges. |
Connect ViewMax MCP in one block of JSON
- 1. Create a key on your API keys page. It is shown once, so save it somewhere.
- 2. Add the ViewMax MCP server with the snippet for your client below.
- 3. Ask for a video.
claude mcp add --transport http viewmax https://viewmaxstudio.net/api/mcp \
--header "Authorization: Bearer YOUR_API_KEY"What the ViewMax MCP server can do
ViewMax MCP gives the model four tools, deliberately. A server that exposes thirty of them buries the model in choices and eats the context window before any work starts. These four cover the whole job:
generate_videoBooks a render from a prompt and returns a job id straight away. Takes model, length, resolution and frame shape.
get_videoChecks a job. Once it is done the result carries a public video URL that anyone can open.
get_credit_balanceHow many credits are left on the key.
list_video_modelsno key neededEvery model with its exact limits and per-second credit price. No key needed.
Rendering runs in the background and takes two to four minutes depending on the model, so booking a clip and collecting it are two separate calls. Your assistant handles the waiting.
What ViewMax MCP costs, before you spend it
The question people actually ask about ViewMax MCP is what a clip is going to cost, and most servers answer it somewhere other than the page you are reading. Here is the whole of it.
- Signing up gives you free credits and does not ask for a card. That is enough to connect ViewMax MCP and render a few clips before you decide anything.
- Renders spend the same credits the ViewMax Studio website does, at the same rates. Prices are per second of video and differ by model; the model catalogue lists every one of them, and
list_video_modelsreturns the same numbers to your assistant so it can quote you a price before it books anything. - A render that fails is refunded automatically. One you cannot afford is refused before it starts, so nothing is taken and no job sits half-finished.
- There is no separate plan for MCP access and no per-seat charge for connecting a client. Credits are the only meter. Pricing has the packages.
Or call the ViewMax HTTP API directly
The ViewMax MCP server is a thin layer over a plain ViewMax HTTP API. Same key, same credits, no MCP client required.
| Method | Path | What it does |
|---|---|---|
| POST | /api/v1/videos | Book a render. Answers 202 with a job id; never waits for the clip. |
| GET | /api/v1/videos/{id} | One job: its status, and its video URL once it is finished. |
| GET | /api/v1/credits | Credit balance. |
| GET | /api/v1/models | The model catalogue with prices. No key needed. |
# Book a render
curl -X POST https://viewmaxstudio.net/api/v1/videos \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"prompt":"a paper boat drifting down a rain gutter, macro lens","duration":"5"}'
# Poll it until status is "completed"
curl https://viewmaxstudio.net/api/v1/videos/JOB_ID \
-H "x-api-key: YOUR_API_KEY"How ViewMax MCP handles async work, limits and errors
The one thing that trips people up when they wire ViewMax MCP, or any video tool, into an agent is that video is slow. Everything below follows from that.
- A clip takes two to four minutes, far past any client’s tool timeout, so
generate_videoreturns a job id and never blocks. The tool descriptions tell the assistant to check back roughly every fifteen seconds and to say what it is doing instead of going quiet. - Each ViewMax MCP key allows 60 requests a minute. A fifteen second poll sits far inside that, even with several renders in flight at once.
- Errors come back as codes, not prose, so an agent can act on them: a refused render, an expired key and a model that rejected a prompt are distinguishable without reading English.
- Finished clips are served from a public URL, because the tools that read them next will not be carrying your session. Treat that link as shareable, because anyone who holds it can fetch the file.
What people build with ViewMax MCP
Connecting ViewMax MCP is only interesting because of what stops being a separate errand. Five things it gets used for:
Faceless shorts, written and rendered in one thread
Ask the assistant for a hook, then have it render each beat as a clip. The script and the clips come out of the same conversation, so a rewrite is a re-render rather than a round trip through three tools.
UGC ad variants
One product, one brief, six angles. Loop the prompt in your agent and let ViewMax MCP book all six renders, then collect them as links you can drop straight into an ad account.
Listing and property videos
Turn a set of stills and a description into a short walkthrough. This is the most common thing people ask ViewMax MCP for after shorts, and it is a good fit because the shot list is short and repeatable.
Hero clips while you are still in the editor
Claude Code is already in your repo. Ask for a five second background loop, get a URL back, and paste it into the component you were editing without opening a browser.
Batch work driven by a script
Because the ViewMax MCP server sits on a plain HTTP API, the same jobs run from a cron task or a CI step. Nothing about ViewMax MCP is locked to a chat window.
ViewMax MCP FAQ
What is ViewMax MCP?
ViewMax MCP is the ViewMax Studio MCP server: a hosted endpoint that follows the Model Context Protocol, so an AI assistant can generate video as a native tool. You add the ViewMax MCP server to Claude, Claude Code, Cursor or Codex once, and from then on asking for a clip in chat books a real render on ViewMax Studio and returns a link to the finished file.
Is ViewMax MCP free?
Signing up gives you free credits and does not ask for a card, so you can connect ViewMax MCP and render a few clips before paying anything. After that, renders spend credits at the same rates the ViewMax Studio website charges. There is no separate subscription for MCP access and no per-seat fee for connecting a client.
How much does one clip cost through ViewMax MCP?
Price depends on the model and the length, and it is quoted per second rather than per clip. The list_video_models tool returns the exact per-second credit price for every model, so your assistant can tell you what a render will cost before it books it. A render you cannot afford is refused before it starts, and a render that fails is refunded automatically.
Which model actually renders the video?
Whichever one you name. ViewMax MCP does not silently pick a provider for you: list_video_models returns the catalogue, and generate_video takes the model as a parameter. If you leave it out, the default is used and the job record still names the model that ran, so you can always see after the fact what produced a given clip.
Does ViewMax MCP work with Cursor, Codex and ChatGPT?
Yes. The ViewMax MCP server speaks Streamable HTTP and is stateless, which is the transport Cursor, Codex, Claude Desktop and Claude Code all support. Any client that can send an HTTP MCP request with an Authorization header can use it. There is nothing to install locally and no Node process to keep running.
How do I install ViewMax MCP?
There is no install. Create an API key in your account settings, then add the server URL and the key to your client, either with a single claude mcp add command or by pasting one block of JSON into the client config. Restart the client and the ViewMax MCP tools appear alongside its built-in ones.
Why does generate_video not return the video straight away?
A clip takes two to four minutes, which is longer than any MCP client will hold a tool call open. So booking and collecting are separate: generate_video returns a job id immediately and get_video checks on it. The tool descriptions tell the assistant to wait about fifteen seconds between checks and to say so rather than going quiet.
Can I use ViewMax MCP without an MCP client?
Yes. The ViewMax MCP server is a thin layer over a public ViewMax HTTP API at /api/v1, and both accept the same key and spend the same credits. If you are writing a script or a backend job rather than working in a chat client, call the endpoints directly and skip MCP entirely.
Connect ViewMax MCP
Create a ViewMax Studio key, paste one block of JSON, and ask your assistant for a clip. Free credits to start, no card.