MCP Server vs VideoGen MCP
A side-by-side look at the MCP Server and VideoGen MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server for multimedia process work as a local process; choose VideoGen MCP for multimedia process over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_models, get_model_schema, run_model.
Choose VideoGen MCP when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
VIDEOGEN_API_KEY, VIDEOGEN_BASE_URL, VIDEOGEN_OAUTH_ISSUER, VIDEOGEN_OAUTH_SUPABASE_PROJECT_URL, VIDEOGEN_OPENAI_APPS_CHALLENGE_TOKEN. - You want tools like
get_getting_started_guidance, get_async_tasks_guidance, get_workflows_guidance.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 65/100 · Great | 84/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | VIDEOGEN_API_KEYVIDEOGEN_BASE_URLVIDEOGEN_OAUTH_ISSUERVIDEOGEN_OAUTH_SUPABASE_PROJECT_URLVIDEOGEN_OPENAI_APPS_CHALLENGE_TOKEN |
| Verified owner | Community listing | Verified |
| GitHub stars | 34 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | 11 | 50 |
| Full listing | View MCP Server | View VideoGen MCP |
Tools & capabilities
MCP Server tools 11
list_modelsSearch the live WaveSpeed model catalog (image, video, audio, 3D). Returns model IDs usable with run_model. Do not invent model IDs — always pick one returned by this tool.get_model_schemaGet a model's real input schema (required fields, properties, defaults). Call this before run_model so inputs match what the model actually accepts.run_modelRun any WaveSpeed model. input keys come from get_model_schema; unknown keys are rejected before submission. Local files: pass "@./path" string values — they are uploaded and replaced with hosted URLs (bare paths are NOT uploaded). Returns the prediction id right away (done=false); call get_prediction with that id and wait_seconds until done=true to get the output URLs. The task keeps running on the server. Pass wait_seconds here to wait for a quick model in the same call.get_priceEstimate the cost of a run before executing it (no charge). Provide the same input you would pass to run_model — pricing often depends on inputs like duration or resolution, and a quote made without them can be lower than the real charge.get_balanceShow the WaveSpeed account credit balance, with the link to top up.list_predictionsList past predictions (run history), newest window first. Defaults to the last 24 hours; pass since/until (ISO or YYYY-MM-DD) for other ranges. Use get_prediction with an id for one task in full.list_billingsList itemized charges and refunds (billing records). Requires an API key with Billing access.get_usageUsage statistics: spend, request counts, daily series and per-model breakdown. Defaults to the last 7 days. Requires an API key with Billing access.delete_predictionsDelete finished predictions from this account's run history, up to 100 at a time. They stop appearing in list_predictions and get_prediction, and this tool cannot bring them back. Runs that are still going are left alone, and only the key's own organization's records are deleted. Ask the user first, and pass confirm: true only after they agreed to delete these ids.upload_fileUpload a local file to WaveSpeed and get its hosted URL (identical bytes reuse the same upload for 24h). Usually unnecessary — run_model handles "@./path" inputs itself.get_predictionFetch the status and outputs of a past or in-flight prediction by id — use to pick up a run that returned done=false. Pass wait_seconds to keep waiting for it to finish.
VideoGen MCP tools 50
get_getting_started_guidanceHow to authenticate, verify with get_me, introduce VideoGen with workflow example prompts, choose workflows vs media tools, and follow VideoGen id conventions. Call when connecting, onboarding, the user asks what VideoGen can do, or how to set up the API or MCP. Equivalent to reading the `guidance://getting-started` MCP resource — provided as a tool for clients that don't read resources directly.get_async_tasks_guidanceHow to handle async workflows, tool executions, and exports: statuses, hosted vs local wait caps, polling with get_* tools, and when webhooks apply outside MCP. Call before polling or when a start tool returns a still-running snapshot. Equivalent to reading the `guidance://async-tasks` MCP resource — provided as a tool for clients that don't read resources directly.get_workflows_guidanceCanonical run → remix → export flow and when to use each workflow tool. Prefer script_to_video for longer narrated / informational videos; keep storyboard_to_video to ≤3 scenes unless the user asks for more. Call before starting a full video project. Equivalent to reading the `guidance://workflows` MCP resource — provided as a tool for clients that don't read resources directly.get_tools_vs_workflows_guidanceWhen to use standalone media tools (automatic model routing for a single asset) versus workflows (full editable professional video). Call when choosing between generate_* tools and workflow tools. Equivalent to reading the `guidance://tools-vs-workflows` MCP resource — provided as a tool for clients that don't read resources directly.script_to_videoPreferred for narrated / informational / explainer videos from text, especially ~1 minute or longer. Turn a verbatim narration script into an editable video with AI-generated visuals and captions. Prefer this over storyboard_to_video unless the user wants a short shot-directed storyboard. For avatar narration, pass actorEntityId and optionally set avatarQuality.voiceover_to_videoBuild an editable video with AI-generated visuals from an uploaded voiceover audio file.slideshow_to_videoBuild an editable narrated video from an uploaded PDF or slideshow file. Upload the file first with upload_file, then pass its fileId. For avatar narration, pass actorEntityId and optionally set avatarQuality.storyboard_to_videoBuild an editable video from an ordered storyboard (frame-by-frame shot list). Every scene needs a visual prompt and may include spoken words. To show a saved product, actor, or visual style, pass productEntityIds, actorEntityIds, or visualStyleEntityId on each scene that should use that entity's reference images (create_entity and add_entity_reference first). A prompt alone does not attach those images. Much more credit-heavy than script_to_video: use at most 3 scenes unless the user explicitly asks for more. Prefer script_to_video for ~1 minute+ narrated / informational videos. If the user has not named a workflow, ask with pros/cons before calling this.prompt_to_video_clipGenerate one short AI video clip from a prompt inside an editable project.list_workflow_runsList workflow runs, most recent first.get_workflow_runFetch the current status and result of a single workflow run.cancel_workflow_runRequest cancellation of an in-progress workflow run.- +38 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.
MCP Server
{
"mcpServers": {
"mcp-215": {
"command": "npx",
"args": [
"-y",
"@wavespeed/mcp"
]
}
}
}
VideoGen MCP
{
"mcpServers": {
"videogen-mcp": {
"command": "npx",
"args": [
"-y",
"@videogen/mcp"
],
"env": {
"VIDEOGEN_API_KEY": "YOUR_VIDEOGEN_API_KEY_HERE",
"VIDEOGEN_BASE_URL": "YOUR_VIDEOGEN_BASE_URL_HERE",
"VIDEOGEN_OAUTH_ISSUER": "YOUR_VIDEOGEN_OAUTH_ISSUER_HERE",
"VIDEOGEN_OAUTH_SUPABASE_PROJECT_URL": "YOUR_VIDEOGEN_OAUTH_SUPABASE_PROJECT_URL_HERE",
"VIDEOGEN_OPENAI_APPS_CHALLENGE_TOKEN": "YOUR_VIDEOGEN_OPENAI_APPS_CHALLENGE_TOKEN_HERE"
}
}
}
}
Frequently asked questions
MCP Server is categorized under Multimedia Process and uses a local stdio subprocess. VideoGen MCP belongs to Multimedia Process and uses a remote HTTP/SSE transport. Pick MCP Server for multimedia process work and VideoGen MCP 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.
MCP Server has no declared pricing — check the project's own site. VideoGen MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 mcp-215 and videogen-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server has a quality signal of 65/100 (Great) with 1 views, 0 installs and 34 GitHub stars. VideoGen MCP has 84/100 (Excellent) with 10 views, 0 installs and 4 GitHub stars.