theme-video-mcp
Related Servers
Alternatives to theme-video-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to create professional YouTube videos using Remotion with a design-system-first approach. Provides 20+ video components, 7 themes, and animated elements optimized for engagement and retention.1522Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables video editing via YAML/JSON edit specs, with validation and rendering using Remotion.2 npmApache 2.0
- AlicenseAqualityCmaintenanceRender HTML/CSS/JS/SVG animations into high-quality MP4 videos. Exposes render tools to AI agents using Playwright (Chromium) and FFmpeg, running locally or remote.2MIT
- AlicenseAqualityAmaintenanceYour coding agent makes the demo video — turns a storyboard.json into a narrated, captioned product-demo MP4; deterministic replay re-renders it in CI at ~$0.24225 npm9MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to turn scripts into narrated videos in YouTube 16:9 or Reels 9:16 formats using HTML pages, Remotion compositions, or HyperFrames layouts, with TTS-driven timing, captions, and optional S3 uploads.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to programmatically scaffold Remotion projects, analyze audio for beat-synced scenes, synthesize voiceovers with word-level timecodes, preview frames, and render finished videos.10 npmMIT
TDQS
Scored across 3 tools
The three tools have clearly separated roles: list_components enumerates scene components, list_assets enumerates available icons/illustrations, and render_video performs the actual rendering. There is no realistic ambiguity between the two list tools because their resource types are distinct.
All tool names follow the same lowercase snake_case verb_noun pattern: list_components, list_assets, and render_video. The verbs 'list' and 'render' are accurate and consistently applied.
Three tools are well-scoped for this narrow server purpose: discover available components, discover available assets, and render a video. Each tool earns its place and there are no redundant or extraneous tools.
The workflow is fully covered: list_components supplies prop schemas for composing scenes, list_assets provides valid asset names, and render_video consumes both to produce the final output with URLs and narration files. Since the catalogs are fixed, additional CRUD operations would be unnecessary.