Vivideo MCP server

• check_accountFree

  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.

• check_configurationFree

  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.

• create_auto_videowrite actionFree

  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.

• create_manual_videowrite actionFree

  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.

• estimate_creditsFree

  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.

• get_videoFree

  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.

• list_avatarsFree

  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.

• list_brand_kitsFree

  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.

• list_modelsFree

  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.

• list_videosFree

  List the account's videos, newest first. Filter by status and limit the count to keep responses small.

• list_voicesFree

  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.

• render_previewFree

  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.

• wait_for_videoFree

  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.

• Code scan7 source files scanned25/25
• Live reliabilityremote reachable in 1560ms20/20
• Tool poisoning13 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 58 days ago12/15
• Maintainer identityregistry namespace matches repository owner6/10

Safety score

86/100

higher than 74% of 1,337 Media servers

Tools

13

the typical Media server has 7

Tools that change things

15%

typical: 4%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Media server answers 100%

Response time

151 ms

faster than 79% of 862 Media servers

Downloads a week

19

more than 6% of 365 Media servers with a package

Vivideo: common questions

Is Vivideo MCP server safe?

Yes, by our scan: it is graded A (86/100). Read the Vivideo safety report

How do I install Vivideo?

It runs remotely at api.vivideo.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Vivideo need an API key?

Yes. The registry entry asks for VIVIDEO_API_KEY, Authorization.

Is Vivideo maintained?

The last commit was 99 days ago (2026-07-28). The latest release is v1.0.2.

Is Vivideo up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Vivideo?

Servers from other publishers that do the same job: SuperCMO MCP server, Sapiens Sintéticos MCP server and Veo MCP server.

How does Vivideo compare with other Media MCP servers?

safety score 86/100 (higher than 74% of 1,337 Media servers); tools 13 (the typical Media server has 7); tools that change things 15% (typical: 4%. Fewer write tools means less an agent can break). Full comparison.