VideoGen MCP vs Mediamcp

A side-by-side look at the VideoGen MCP and Mediamcp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

VideoGen MCP logoVideoGen MCPMultimedia Process · Remote HTTP/SSEOfficial VideoGen MCP server for creating product demos, ecommerce ads, and marketing videos from AI assistants. Generate and edit videos, images, voiceovers, music, and avatars; upload assets, remix projects, and export finished videos. Tools include script_to_video, storyboard_to_video, generate_image, text_to_speech, and export_project. Connect remotely at https://mcp.videogen.io/mcp with OAuth or your VideoGen API key, or run npx -y @videogen/mcp locally. Setup: https://videogen.io/videogen-mcp. Developer docs: https://docs.videogen.io/libraries/mcp. Callable tool reference: https://github.com/video-gen/videogen-mcp/blob/main/TOOL_SCHEMAS.md. Complete input and output JSON schemas for 50 hosted tools: https://raw.githubusercontent.com/video-gen/videogen-mcp/main/tool-schemas.json.83ExcellentAuth: api key requiredMediamcp logoMediamcpMultimedia Process · Local subprocess (stdio)Image generation and editing plus video generation (Veo, Sora, Seedance) via OpenRouter or any OpenAI-compatible API. Saves files to disk with token-cheap inline previews, resumable video jobs, live model listing, and a config-diagnostics tool. npx -y mediamcp.65GreatAuth: api key required

Verdict: choose VideoGen MCP for multimedia process work over a hosted endpoint; choose Mediamcp 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?

VideoGen MCP logoChoose 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.
Explore VideoGen MCP

Mediamcp logoChoose Mediamcp when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: OPENROUTER_API_KEY.
  • You want tools like generate_image, edit_image, generate_video.
Explore Mediamcp

Feature & specification comparison

Rows where the two servers differ are marked.

SpecVideoGen MCP logoVideoGen MCPMediamcp logoMediamcp
CategoryMultimedia ProcessMultimedia Process
Quality signal83/100 · Excellent65/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthAPI key requiredAPI key required
PricingBYOK (pay the provider)BYOK (pay the provider)
Required env varsVIDEOGEN_API_KEYVIDEOGEN_BASE_URLVIDEOGEN_OAUTH_ISSUERVIDEOGEN_OAUTH_SUPABASE_PROJECT_URLVIDEOGEN_OPENAI_APPS_CHALLENGE_TOKENOPENROUTER_API_KEY
Verified owner VerifiedCommunity listing
GitHub stars44
Directory activity 15 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools496

Tools & capabilities

VideoGen MCP tools 49

  • 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. 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.
  • +37 more on the listing page

Mediamcp tools 6

  • generate_imageGenerate one or more images from a text prompt using a cloud AI model. Every image is saved to disk and its absolute path is returned, along with a small inline preview. Use edit_image instead when starting from an existing image.
  • edit_imageEdit or transform existing image(s) with a text instruction — restyle, add or remove elements, change background, or combine several images into one scene. The result is saved to disk and its absolute path is returned, along with a small inline preview.
  • generate_videoGenerate a video from a text prompt, and optionally from an input image (image-to-video). Async job: starts generation, then waits and polls. Video generation typically takes 1-5 minutes. The finished file is saved to disk and its absolute path is returned. If waiting times out, a polling_url is returned — pass it to check_video_status later instead of starting a new (billed) job. For image-to-video, pass first_frame_image so the clip animates from that exact picture (e.g. a still produced by generate_image). Image inputs require an image-to-video-capable model such as 'bytedance/seedance-2.0', 'bytedance/seedance-2.0-fast', or 'google/veo-3.1'.
  • check_video_statusCheck a previously started video generation job (from generate_video's polling_url or video id). If the job has completed, downloads the video, saves it to disk, and returns the absolute path.
  • list_modelsList image- and video-capable model slugs available on the configured endpoint, with pricing where known. Use this to pick a `model` value for generate_image, edit_image, or generate_video.
  • check_configDiagnose the mediamcp server setup: endpoint, API key presence and validity, default models, and output directory writability. Run this first when any other mediamcp tool fails.

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.

VideoGen MCP

mcpServers (Claude Desktop / Cursor)
{
  "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"
      }
    }
  }
}

Mediamcp

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "legolev-mediamcp": {
      "command": "npx",
      "args": [
        "-y",
        "mediamcp"
      ],
      "env": {
        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

VideoGen MCP is categorized under Multimedia Process and uses a remote HTTP/SSE transport. Mediamcp belongs to Multimedia Process and uses a local stdio subprocess. Pick VideoGen MCP for multimedia process work and Mediamcp 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.

VideoGen MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Mediamcp 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 videogen-mcp and legolev-mediamcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, VideoGen MCP has a quality signal of 83/100 (Excellent) with 15 views, 0 installs and 4 GitHub stars. Mediamcp has 65/100 (Great) with 7 views, 0 installs and 4 GitHub stars.