# VibeFrame

> CLI-first video workflow runtime with an MCP surface for briefs-to-renders.

- **Category:** Editing & Post
- **Vendor:** VibeFrame (vericontext) (official)
- **Pricing:** freemium
- **Verified:** 2026-06-28

## What it does

VibeFrame is an agentic video workflow runtime: a coding agent turns a brief into storyboard files, generated assets, Hyperframes scenes, reviewed renders, and final MP4s. Its MCP server exposes the same engine as typed tools for project init, build, render, generation, editing, audio, detection, inspection, and timeline operations, with dry runs and cost gates for paid providers.

## Connect

- Claude Code: `claude mcp add vibeframe --scope project -- npx -y @vibeframe/mcp-server`
- Local: `npx -y @vibeframe/mcp-server`

**Auth:** api_key (env `FAL_API_KEY`) — Provider keys are bring-your-own: FAL_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, ELEVENLABS_API_KEY and others depending on the models you enable.

## Capabilities

`storyboard-to-video` · `cloud-render` · `text-to-video` · `image-to-video` · `captioning` · `audio-generation` · `quality-review` · `cost-gates`

## Sample tools

`project_list` · `init` · `build` · `render` · `generate_image` · `generate_video` · `edit_caption` · `audio_duck` · `inspect_review` · `timeline_create`

## Field notes

MIT, npm @vibeframe/mcp-server 0.113.11. Requires Node 20+, FFmpeg, and Chrome/Chromium; AI generation bills whichever provider keys you wire in. The project warns that the CLI is the stable runtime and MCP is the host surface, so shell-capable agents may prefer direct `vibe` commands for long builds.

## Links

- Site: https://vibeframe.ai
- Docs: https://github.com/vericontext/vibeframe#readme
- Repo: https://github.com/vericontext/vibeframe

---

Structured data: https://mcp.film/api/mcps/vibeframe.json · Directory: https://mcp.film