mcpbeat

Vivideo MCP Server

io.github.egocen-vivideo/vivideo
answering

Vivideo is answering right now. Last checked 8 min ago. 496 installs a week from npm. It exposes 13 tools. Last commit 28 Jul 2026.

AI video generation via the Vivideo API: auto or manual mode, avatars, voices, brand kits.

Installs per day peak 213 · avg 16
a month agotoday
Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
13
Tools
read from the server
250 ms
Response time
average over 24h
496
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add vivideo --transport http https://api.vivideo.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "vivideo": {
      "url": "https://api.vivideo.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.vivideo]
url = "https://api.vivideo.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "vivideo": {
      "url": "https://api.vivideo.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "vivideo": {
      "url": "https://api.vivideo.ai/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

account
check_account
Get the account plan, premium status, and remaining credit balance. Use this to decide whether the user can generate a video (rendering needs a premium plan and enough credits). Returns plan, premium, credits, free_video_available, and links (upgrade / buy_credits). Cheap and safe to call often.
auto
create_auto_video
Create a video in AUTO mode: Vivideo writes the script and produces a complete AI-avatar video from your prompt. Returns immediately with a video id and status "processing" (paid) or "preview" (free accounts — see the preview field and upgrade link). Then call wait_for_video or get_video. An Idempotency-Key is sent automatically so a retry never creates a duplicate. Rendering requires a premium plan and credits.
avatars
list_avatars
List available avatars for auto-mode videos (the stock catalogue plus the account's own avatars). Stock avatars are grouped by person, each with a `looks` array — pass a looks[].avatar_id (or an owned avatar's id) as `avatar_id` in create_auto_video. Use `search`/`limit` to keep responses small.
brand
list_brand_kits
List the account's brand kits (logo, colors, fonts, motion style). Returns brand_ref ids to pass as `brand_kit_id` in create_auto_video to produce an on-brand video.
configuration
check_configuration
Check whether a Vivideo API key is present on this request. Call this FIRST. Returns { configured: boolean }. If false, ask the user to add an Authorization: Bearer vv_live_... header to the MCP server config (a key from https://app.vivideo.ai/account/api-keys). Never asks for or exposes the key.
estimate
estimate_credits
Estimate the credits a generation will cost, from the published per-model rates — BEFORE creating it. This is an estimate, not a charge; the exact amount is returned as credits_charged when you create the video. Use it with check_account to confirm the user can afford the request.
manual
create_manual_video
Create a video in MANUAL mode: send your prompt straight to a specific model (get ids/options from list_models). The operation is inferred from inputs — add image_url for image-to-video. resolution/duration/aspect_ratio must match the model (an invalid value returns a 400 listing what is allowed). Returns a video id and status; then wait_for_video or get_video. Idempotency handled automatically.
models
list_models
List the video models available for MANUAL mode plus the auto-generate pipeline (id "vivideo-auto"). Each model lists its operations, allowed durations, resolutions, aspect ratios, style presets and per-second credit rate — use these to build a valid create request. Filter with `mode` to keep the response small.
render
render_preview
For FREE accounts only: after the user upgrades, render a video that was returned as status "preview". Charges run on the same project (the first video after upgrading is free). If the video is already rendering/complete, returns its current state. If the account is still free, returns an upgrade_required error with an upgrade link.
video
get_video
Get a video's current status and result. status is one of queued | processing | completed | failed | preview. When completed, video_url is the MP4. When failed, credits are refunded and error explains why. Cheap; prefer wait_for_video for polling instead of calling this in a tight loop.
videos
list_videos
List the account's videos, newest first. Filter by status and limit the count to keep responses small.
voices
list_voices
List available voices for auto-mode videos. Returns voice ids to pass as `voice_id` in create_auto_video. Filter by language/gender/search and cap with `limit`. Voice cloning is not available via the API.
wait
wait_for_video
Wait for a video to reach a terminal state (completed / failed / preview), then return it. Polls safely at the API-suggested interval for up to ~20 seconds per call (HTTP requests are time-capped). If it does not finish in time it returns { timed_out: true } with the latest status — simply call it again with the same id to keep waiting. It never blocks indefinitely or over-polls.

Endpoints

URLTransportStateLatencyChecked
https://api.vivideo.ai/mcp streamable-http answering 186 ms 8 min ago

Vivideo — questions

Answers built from our own checks of this server.

What can Vivideo do?
It exposes 13 tools, read directly from the server on our last check. Among them: check_account, check_configuration, create_auto_video, create_manual_video, estimate_credits, get_video and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Vivideo working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 250 ms. The bar chart above shows every period we have measured.
How do I connect Vivideo?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Vivideo need an API key?
No. Vivideo completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Vivideo?
It answers our handshake in 250 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Vivideo?
The npm package @vivideo/mcp was installed 496 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Vivideo open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.