Skip to main content
mcpSource-backed

Short Video Maker MCP Server

MCP and REST server for creating short-form videos from scene text, Pexels search terms, text-to-speech, captions, background music, Whisper captions, FFmpeg, and Remotion rendering.

by David Gyori · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://raw.githubusercontent.com/gyoridavid/short-video-maker/main/README.md, https://github.com/gyoridavid/short-video-maker
Brand
Short Video Maker
Brand domain
github.com
Safety notes
Short Video Maker runs an HTTP server with MCP SSE routes and REST routes for creating and serving generated videos., The create-short-video tool queues video rendering work that can consume CPU, memory, disk, browser rendering resources, and optional GPU resources., Generated videos combine user-provided narration text, Pexels search terms, downloaded background clips, local music assets, TTS output, captions, and rendered media., The server stores generated videos and temporary files under its configured data directory., Validate scene text, search terms, claims, branding, and rights before publishing generated videos to TikTok, Instagram, YouTube, or other platforms.
Privacy notes
`PEXELS_API_KEY` is sent to the Pexels API when searching for background videos., Scene text, search terms, generated narration, captions, video IDs, logs, output filenames, and render status can reveal campaign ideas, private scripts, brand plans, or client work., Generated files remain on disk until removed according to the deployment's data-directory and retention practices., Pexels requests, model downloads, Docker pulls, npm installs, and platform uploads may expose network metadata to third parties outside the MCP client.
Author
David Gyori
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

25 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/5 ready
Account & credentials1Install & runtime2Review & approval1General125 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 4 risk areas. Review closely: network access, third-party handling.

4 areas
  • SafetyNetwork accessShort Video Maker runs an HTTP server with MCP SSE routes and REST routes for creating and serving generated videos.
  • SafetyLocal filesThe create-short-video tool queues video rendering work that can consume CPU, memory, disk, browser rendering resources, and optional GPU resources.
  • SafetyNetwork accessGenerated videos combine user-provided narration text, Pexels search terms, downloaded background clips, local music assets, TTS output, captions, and rendered media.
  • SafetyLocal filesThe server stores generated videos and temporary files under its configured data directory.
  • SafetyGeneralValidate scene text, search terms, claims, branding, and rights before publishing generated videos to TikTok, Instagram, YouTube, or other platforms.
  • PrivacyThird-party handling`PEXELS_API_KEY` is sent to the Pexels API when searching for background videos.
  • PrivacyLocal filesScene text, search terms, generated narration, captions, video IDs, logs, output filenames, and render status can reveal campaign ideas, private scripts, brand plans, or client work.
  • PrivacyLocal filesGenerated files remain on disk until removed according to the deployment's data-directory and retention practices.
  • PrivacyNetwork accessPexels requests, model downloads, Docker pulls, npm installs, and platform uploads may expose network metadata to third parties outside the MCP client.

Disclosure: MIT-licensed open-source project. The upstream README promotes a related community and tutorial content; this entry focuses on the source-backed MCP and REST video-generation server.

Safety notes

  • Short Video Maker runs an HTTP server with MCP SSE routes and REST routes for creating and serving generated videos.
  • The create-short-video tool queues video rendering work that can consume CPU, memory, disk, browser rendering resources, and optional GPU resources.
  • Generated videos combine user-provided narration text, Pexels search terms, downloaded background clips, local music assets, TTS output, captions, and rendered media.
  • The server stores generated videos and temporary files under its configured data directory.
  • Validate scene text, search terms, claims, branding, and rights before publishing generated videos to TikTok, Instagram, YouTube, or other platforms.

Privacy notes

  • `PEXELS_API_KEY` is sent to the Pexels API when searching for background videos.
  • Scene text, search terms, generated narration, captions, video IDs, logs, output filenames, and render status can reveal campaign ideas, private scripts, brand plans, or client work.
  • Generated files remain on disk until removed according to the deployment's data-directory and retention practices.
  • Pexels requests, model downloads, Docker pulls, npm installs, and platform uploads may expose network metadata to third parties outside the MCP client.

Prerequisites

  • Node.js or Docker available on the machine that will run the video server.
  • Pexels API key configured through `PEXELS_API_KEY`.
  • Enough CPU, memory, and disk for Whisper, Kokoro, FFmpeg, Remotion, temporary files, and rendered videos.
  • MCP client that can connect to an SSE MCP endpoint.
  • Usage rights reviewed for prompts, narration text, generated captions, music, background clips, and final publishing destination.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
25 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
MIT-licensed open-source project. The upstream README promotes a related community and tutorial content; this entry focuses on the source-backed MCP and REST video-generation server.
Full copyable content
{
  "mcpServers": {
    "short-video-maker": {
      "url": "{short-video-maker-sse-url}"
    }
  }
}

About this resource

Content

Short Video Maker is an MCP and REST server for generating short-form videos from structured scene descriptions. Each scene provides narration text and video search terms; the server then uses Kokoro TTS, Whisper captions, Pexels background-video search, local music assets, FFmpeg, and Remotion to render a finished video.

Use it when Claude should help draft a reviewed scene plan, submit it to a local or hosted video-generation service, and poll for status. It is especially suited to agent workflows that already need a self-hosted alternative to API-only video generation, but it still needs careful review before publishing generated media.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, npm metadata, license, package metadata, MCP router, server router, configuration, queue implementation, and Pexels integration for current behavior.

Features

  • Run as a Node or Docker-hosted service with MCP SSE and REST endpoints.
  • Expose create-short-video for queueing a video from scenes and render configuration.
  • Expose get-video-status for checking whether a queued render is processing, ready, or failed.
  • Build scenes from narration text plus Pexels search terms.
  • Support portrait and landscape orientations.
  • Choose caption placement, caption background color, voice, music mood, and music volume.
  • Generate English narration with Kokoro TTS.
  • Generate captions with Whisper.
  • Fetch background videos from Pexels using a configured API key.
  • Render with Remotion and FFmpeg.
  • Serve a web UI and REST API alongside the MCP endpoint.

Installation

Docker is the upstream-recommended path for most users. Start one of the upstream images with PEXELS_API_KEY set and enough memory and disk for model downloads, temporary render assets, and final videos.

For npm-based usage, install or run the package after satisfying the platform requirements:

npx short-video-maker

Then connect an MCP client to the server's SSE endpoint:

{
  "mcpServers": {
    "short-video-maker": {
      "url": "{short-video-maker-sse-url}"
    }
  }
}

The upstream README currently lists Linux and macOS as supported for npm usage and notes that Windows is not supported at the moment.

Use Cases

  • Draft a short educational video from reviewed scene narration and search terms.
  • Generate background-video-and-caption drafts for YouTube Shorts, Instagram Reels, or TikTok-style formats.
  • Use Claude to turn a storyboard into the MCP create-short-video scene structure.
  • Poll render status from an automation workflow before collecting output.
  • Prototype faceless-video workflows without calling a hosted video-generation API for every step.
  • Pair n8n, Claude, or another agent workflow with a self-hosted video-rendering service.

Safety and Privacy

Review the creative brief before approving a render. The tool can turn private drafts, campaign ideas, scripts, or customer content into generated media on disk. Generated voiceover, captions, background clips, music, and final videos may carry copyright, licensing, platform-policy, accessibility, misinformation, or brand-safety obligations.

Treat the server as a resource-heavy media pipeline. Rendering can consume significant CPU, memory, disk, browser-rendering capacity, and optional GPU resources. Keep PEXELS_API_KEY out of prompts and logs, watch data-directory retention, and review Pexels and publishing-platform terms before posting outputs externally.

Duplicate Check

No gyoridavid/short-video-maker, Short Video Maker MCP Server, or matching source URL entry was found in content/mcp or README.md.

Source citations

Add this badge to your README

Show that Short Video Maker MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/short-video-maker-mcp-server.svg)](https://heyclau.de/entry/mcp/short-video-maker-mcp-server)

How it compares

Short Video Maker MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

MCP and REST server for creating short-form videos from scene text, Pexels search terms, text-to-speech, captions, background music, Whisper captions, FFmpeg, and Remotion rendering.

Open dossier

MCP server and CLI for AI image and video generation with gallery search, prompt enhancement, model listing, local preferences, ComfyUI workflows, MeiGen Cloud, and OpenAI-compatible provider support.

Open dossier

Unity MCP server, plugin, CLI, and skill generator for controlling Unity Editor and runtime projects from MCP clients through built-in game-dev tools.

Open dossier

MCP server for controlling DaVinci Resolve Studio through the official scripting API, with tools for projects, timelines, media pools, render setup, review markers, grading, Fusion, Fairlight, and source-safe media analysis.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandMeiGen AI Design MCP logoMeiGen AI Design MCPAI Game Developer logoAI Game DeveloperDaVinci Resolve MCP Server logoDaVinci Resolve MCP Server
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorDavid GyoriMeiGenIvan MurzakSamuel Gursky
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Harness
Source repo
Safety notesShort Video Maker runs an HTTP server with MCP SSE routes and REST routes for creating and serving generated videos. The create-short-video tool queues video rendering work that can consume CPU, memory, disk, browser rendering resources, and optional GPU resources. Generated videos combine user-provided narration text, Pexels search terms, downloaded background clips, local music assets, TTS output, captions, and rendered media. The server stores generated videos and temporary files under its configured data directory. Validate scene text, search terms, claims, branding, and rights before publishing generated videos to TikTok, Instagram, YouTube, or other platforms.MeiGen can submit image and video generation jobs to external providers or a local ComfyUI backend. Image and video generation may spend credits, use paid APIs, or consume local GPU resources depending on the configured provider. Local reference images can be compressed and uploaded through the configured upload gateway before being sent to API providers. Video generation can take minutes, may time out at the MCP client, and should not be retried blindly because jobs or credits may already be in progress. ComfyUI workflow import and modification can run local workflows; review workflow JSON and custom nodes before use.AI Game Developer can create, move, copy, modify, and delete Unity assets, scenes, GameObjects, components, scripts, packages, and generated project files. Tools include dynamic C# script execution, C# reflection method lookup and calls, package installation/removal, Unity test execution, editor state changes, play mode control, screenshots, and profiler access. The MCP server supports streamable HTTP and stdio; HTTP deployments should require a bearer token and stay bound to trusted interfaces. Server variables include optional authorization and webhook settings; webhook endpoints can receive tool, prompt, resource, connection, and authorization events. Unity runtime connections can expose compiled game state or in-game behavior to an MCP client, not just editor-only project data. Use source control, backups, tool filtering, and explicit review before allowing destructive tools such as asset deletion, package removal, script execution, or reflection calls.DaVinci Resolve MCP Server can launch or reconnect to Resolve, switch pages, create or open projects, modify timelines, manage media pools, write markers, change render settings, and queue jobs. Extension-authoring tools can install or remove Resolve scripts, Fuses, DCTLs, ACES DCTLs, presets, and page scripts. Source media is intended to remain immutable by default, but operators must still review requests that relink, replace, transcode, proxy, render, export, or create media derivatives. The default server is local stdio, but the local control panel starts a single-user browser server; keep it on trusted local interfaces only. Require confirmation before deleting projects, replacing clips, changing project settings, installing extensions, updating metadata, or queuing renders. Keep Resolve external scripting set to `Local` unless you have a separate remote-control security plan.
Privacy notes`PEXELS_API_KEY` is sent to the Pexels API when searching for background videos. Scene text, search terms, generated narration, captions, video IDs, logs, output filenames, and render status can reveal campaign ideas, private scripts, brand plans, or client work. Generated files remain on disk until removed according to the deployment's data-directory and retention practices. Pexels requests, model downloads, Docker pulls, npm installs, and platform uploads may expose network metadata to third parties outside the MCP client.API tokens, OpenAI-compatible credentials, provider base URLs, upload gateway URLs, ComfyUI URLs, preferences, recent generations, prompts, model IDs, and output paths can reveal private creative workflows. Uploaded reference images may become public URLs through the configured upload gateway before generation. Prompts, reference images, generated image URLs, generated video URLs, saved outputs, and favorite prompts can contain client work, brand plans, product images, personal likenesses, or unreleased campaigns. Keep secrets in MCP client environment configuration, review generated media before sharing, and remove local outputs when retention is no longer needed.Tool calls may expose Unity project paths, asset names, scene hierarchy, serialized object data, scripts, logs, screenshots, profiler metrics, test output, package metadata, and runtime state. MCP config files and Unity plugin config can contain server URLs, connection modes, bearer tokens, authorization settings, enabled tool IDs, and cloud or local endpoint details. Optional webhooks can receive tool, prompt, resource, connection, authorization, and token-bearing request data. Screenshots from Game View, Scene View, cameras, or isolated GameObjects may include proprietary artwork, level design, UI, debug overlays, or unreleased game content. Generated skills and AI-client configuration files can reveal available tools, project structure, installed packages, and local workflow assumptions.Project names, timelines, clip names, media paths, markers, metadata, render paths, transcripts, thumbnails, analysis artifacts, logs, and Resolve scripting paths can be exposed to the MCP client. Media analysis can produce sidecar files, scratch artifacts, frame paths, transcripts, searchable indexes, and reports that may include private footage details. Host-chat visual analysis can expose selected frame images to the active MCP client or vision-capable model provider. Local logs and analysis reports may contain absolute media paths, project names, clip metadata, speaker text, visual descriptions, and render settings. Store generated analysis artifacts and exports inside approved project or scratch directories and delete them when no longer needed.
Prerequisites
  • Node.js or Docker available on the machine that will run the video server.
  • Pexels API key configured through `PEXELS_API_KEY`.
  • Enough CPU, memory, and disk for Whisper, Kokoro, FFmpeg, Remotion, temporary files, and rendered videos.
  • MCP client that can connect to an SSE MCP endpoint.
  • Node.js 18 or newer.
  • MCP client that can launch a local Node stdio server.
  • Optional MeiGen API token, OpenAI-compatible API key, or local ComfyUI workflow configuration for generation tools.
  • Provider pricing, credits, model limits, and content policy reviewed before image or video generation.
  • Unity project using Unity 2022.3 or newer for the current package metadata.
  • Unity Hub or a local Unity Editor installation.
  • Node.js 20.19 or newer, or Node.js 22.12 or newer, for `unity-mcp-cli`.
  • An MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, GitHub Copilot, Cline, or another supported client.
  • DaVinci Resolve Studio 18.5 or newer; the free edition does not support the required external scripting API.
  • Resolve external scripting set to `Local`.
  • Python 3.10 or newer, with Python 3.10-3.12 recommended for the broadest Resolve compatibility.
  • A local MCP client that can launch stdio servers under the same user account that operates Resolve.
Install
Run the upstream Docker image or `npx short-video-maker` with `PEXELS_API_KEY` set, then connect an MCP client to the server's `/mcp/sse` endpoint.
Run `npx -y meigen` from an MCP client, or use the upstream plugin/init commands after reviewing provider credentials and generated-media costs.
npm install -g unity-mcp-cli && unity-mcp-cli install-plugin ./MyUnityProject
npx davinci-resolve-mcp setup
Config
{
  "mcpServers": {
    "short-video-maker": {
      "url": "{short-video-maker-sse-url}"
    }
  }
}
{
  "mcpServers": {
    "meigen": {
      "command": "npx",
      "args": ["-y", "meigen"],
      "env": {
        "MEIGEN_API_TOKEN": "{meigen-api-token}"
      }
    }
  }
}
Manual-only setup:
npm install -g unity-mcp-cli
unity-mcp-cli install-plugin ./MyUnityProject
unity-mcp-cli open ./MyUnityProject
{
  "mcpServers": {
    "davinci-resolve": {
      "command": "npx",
      "args": [
        "davinci-resolve-mcp",
        "server"
      ],
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.