@vibeframe/mcp-server

What it does

VibeFrame is an agentic video workflow system that turns written briefs into storyboards, design documents, generated assets, and final MP4 renders. The MCP server integrates VibeFrame into Claude Code, Cursor, and other AI agents, enabling them to scaffold projects and iterate on STORYBOARD.md and DESIGN.md files that drive composition and rendering. The system is CLI-first; agents typically interact by editing project files and triggering builds rather than through direct MCP tool calls. VibeFrame routes media generation (images, narration, music, motion graphics) through pluggable AI providers and produces deterministic reports for cost gating and safety.

Who it's for

Backend engineers integrating video generation into agent-driven workflows. Product teams using Claude Code or Cursor who want to generate promotional or demo videos from rough briefs without custom infrastructure. Developers who prefer CLI-first tooling with machine-readable JSON output, dry-run modes, and cost-cap controls over interactive chat-based editing.

Common use cases

• Ask Claude Code or Cursor to research a topic and refine STORYBOARD.md and DESIGN.md to shape the video structure before rendering
• Generate product launch or feature-demo videos by iterating storyboards with an agent and validating builds with dry-run output
• Embed video generation as a repeatable step in coding agent workflows, with cost caps and deterministic build reports
• Create multi-scene compositions with AI-generated images, narration, and music via pluggable providers
• Remix or edit existing media using VibeFrame's EDIT, REMIX, and AUDIO command lanes

Setup pitfalls

• One secret found in the codebase—audit the repository and rotate any exposed credentials before deploying in shared environments
• Requires AI provider API keys (image generation, narration, music)—configure .env or environment variables with your service credentials before running builds
• Filesystem write access required—VibeFrame creates project directories, temporary assets, and rendered video files; ensure proper sandbox or volume isolation
• FFmpeg must be installed on the host—VibeFrame calls FFmpeg for composition and rendering; verify installation before the first build