ClipTalk vs Vivideo
A side-by-side look at the ClipTalk and Vivideo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ClipTalk for multimedia process work over a hosted endpoint; choose Vivideo for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ClipTalk when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
list_templates, plan_from_template, create_from_template.
Choose Vivideo when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You want tools like
check_configuration, check_account, list_models.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 69/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 22 | 13 |
| Full listing | View ClipTalk | View Vivideo |
Tools & capabilities
ClipTalk tools 22
list_templatesList the video formats (faceless story, UGC ad, explainer, quiz…) and what each needsplan_from_templateDry run: returns the script and the credit price; creates and charges nothingcreate_from_templateMake a finished video from a format and a sentence, topic or scriptcreate_videoMake a video scene by scene: your media, AI images and clips, presenters, motion graphicsget_motion_dialectReference for writing custom motion-graphics sceneslist_videosList your videosget_videoA video's status and download linkget_video_assetsA video's timeline, scenes and assets, ready to editmake_contact_sheetOne image of frames across the whole video, so the assistant can check itedit_videoChange captions, music, voice, scenes, layout, speed, trims and silencesrender_videoRe-render a video to a new MP4generate_mediaGenerate a single image, clip, voiceover or talking presenter into your library- +10 more on the listing page
Vivideo tools 13
check_configurationCheck whether a Vivideo API key is configured for this MCP server. Call this FIRST. Returns { configured: boolean }. If false, ask the user to set the VIVIDEO_API_KEY environment variable (a key from https://app.vivideo.ai/account/api-keys) and restart the MCP server. Never asks for or exposes the key.check_accountGet 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.list_modelsList 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_avatarsList 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_voicesList 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.list_brand_kitsList 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.estimate_creditsEstimate 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.create_auto_videoCreate 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_videoCreate 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.get_videoGet 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.wait_for_videoWait for a video to reach a terminal state (completed / failed / preview), then return it. Polls safely at the API-suggested interval up to a timeout. If it does not finish in time it returns { timed_out: true } with the latest status so you can hand control back and call again later — it never blocks indefinitely or over-polls.list_videosList the account's videos, newest first. Filter by status and limit the count to keep responses small.- +1 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ClipTalk
{
"mcpServers": {
"cliptalk": {
"url": "https://www.cliptalk.pro/mcp"
}
}
}
Vivideo
{
"mcpServers": {
"vivideo": {
"command": "npx",
"args": [
"-y",
"@vivideo/mcp"
]
}
}
}
Frequently asked questions
ClipTalk is categorized under Multimedia Process and uses a remote HTTP/SSE transport. Vivideo belongs to Multimedia Process and uses a local stdio subprocess. Pick ClipTalk for multimedia process work and Vivideo for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
ClipTalk is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Vivideo has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cliptalk and vivideo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ClipTalk has a quality signal of 69/100 (Great) with 0 views, 0 installs and 0 GitHub stars. Vivideo has 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars.