Pexels vs VideoGen MCP
A side-by-side look at the Pexels and VideoGen MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
PexelsMultimedia Process · Local subprocess (stdio)Pexels MCP.55GoodAuth: not declaredVerdict: choose Pexels 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 Pexels when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_PEXELS_KEY. - You want tools like
photo_search, photo_curated, photo.
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 | Pexels | |
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 55/100 · Good | 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 | PLATFORM_PEXELS_KEY | VIDEOGEN_API_KEYVIDEOGEN_BASE_URLVIDEOGEN_OAUTH_ISSUERVIDEOGEN_OAUTH_SUPABASE_PROJECT_URLVIDEOGEN_OPENAI_APPS_CHALLENGE_TOKEN |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 4 |
| Directory activity | 2 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | 8 | 50 |
| Full listing | View Pexels | View VideoGen MCP |
Tools & capabilities
Pexels tools 8
photo_searchSearch Pexels photos by keyword (required); returns paginated results with image URLs in multiple sizes, photographer name, and attribution link.photo_curatedFetch Pexels' curated editorial photo feed; returns paginated photo objects with image URLs in multiple sizes (original, large, medium, small, tiny) and photographer info.photoFetch full metadata for a single Pexels photo by numeric id, including all sized image URLs, photographer name/URL, dimensions, and alt text.video_searchSearch Pexels videos by keyword (required); returns paginated results with video file URLs at multiple resolutions, duration, and videographer info.video_popularFetch Pexels' popular video feed; returns paginated video objects with file URLs at multiple resolutions, duration, and videographer info.videoFetch full metadata for a single Pexels video by numeric id, including file URLs at all available resolutions, duration, width, height, and videographer attribution.featured_collectionsList Pexels' featured curated collections; returns collection id, title, description, and media counts for photos and videos.collection_mediaFetch all photos and videos inside a specific Pexels collection by string id; returns paginated mixed media objects with URLs and metadata.
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.
Pexels
{
"mcpServers": {
"pexels-3": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-pexels"
],
"env": {
"PLATFORM_PEXELS_KEY": "YOUR_PLATFORM_PEXELS_KEY_HERE"
}
}
}
}
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
Pexels 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 Pexels 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.
Pexels 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 pexels-3 and videogen-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pexels has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. VideoGen MCP has 84/100 (Excellent) with 10 views, 0 installs and 4 GitHub stars.