Clipwave

Description

Generate video and images, then cut them together on a real multi-track timeline — and export an MP4. **Two ways in.** `media_forge_generate` makes one direct model call across the Media Forge catalogue (Seedance, Kling, Veo, Sora, WAN, Flux, Nano Banana); it is async, so you poll `job_status` for the result. The `video_editor_*` tools open a persistent project with a shared asset library and per-video timelines. **The editor loop.** Generate or upload, and the asset lands in the library. Place it with `video_editor_add_clip` on a video / voice / sfx / music track. Inspect with `video_editor_get_timeline`, then edit deterministically by clip id — add, remove, reorder, set an ffmpeg transition, import or export SRT/VTT subtitles — and `video_editor_export` stitches an MP4. Large files skip the request body via presigned upload. Agents and humans edit the same project: what an agent builds over MCP is visible and editable in the Clipwave dashboard, and the other way round. **Auth.** Sign in with OAuth — no key to paste. Headless agents can send a `cw_live_…` API key instead. Read-only tools and deterministic timeline operations are free; generation spends Clipwave credits.

Community Metrics

Categories

• mcp

Tags

• mcp
• smithery

Capabilities

• Local MCP server

Information