Clipwave
io.clipwavePublished by clipwave.ioOfficial publisherv0.1.0Updated Oct 24, 2026
Generate video and images, edit them on a real multi-track timeline, and export an MP4.
Overview
Clipwave is a hosted MCP server that lets an assistant generate video and image shots, edit them on a multi-track timeline, and export an MP4.
- What you can do
- Generate AI video and image shots from text prompts, choosing a model, submitting jobs and polling status, with a model catalogue to read from and a job status check to follow progress, plus a free read-only family of get and list tools for projects, assets and jobs, and a shared asset library to draw on. Edit on a per-video multi-track timeline with video, voice, sfx and music tracks, placing, removing and reordering clips, setting trims and transitions, and burning in captions. Export the finished timeline as an MP4 and get back a URL. Work inside projects with a shared asset library, and use the bundled skills and commands for generation and editing workflows.
- When to use it
- Use it when you want an assistant to go past a single generated clip and carry a short video through to a finished file: generating shots, assembling them on a timeline with transitions and captions, and exporting vertical or other formats. Suited to short social or ad-style videos and to agents that need a hosted editing pipeline rather than local media tools.
- Requirements
- A remote streamable HTTP endpoint at clipwave.io with OAuth 2.0 and dynamic client registration, so no key needs copying for interactive use. A Clipwave account is required. For headless or CI use, an API key created in the dashboard is sent as an Authorization Bearer header. A stdio package exists for clients that cannot reach a remote server.
Installation
In SourceWeft
- Open Clipwave in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.clipwave%2Fclipwave/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"clipwave": {
"type": "http",
"url": "https://clipwave.io/api/mcp"
}
}
}README
Clipwave for Claude
Give Claude a real video editor. Generate shots, cut them on a multi-track timeline, burn in captions, and export an MP4 — without leaving the chat.
Most media integrations stop at "here is a generated clip." Clipwave keeps going: projects, a shared asset library, per-video timelines with video/voice/sfx/music tracks, trims, transitions, subtitles, and a real export.
Then run /mcp, pick clipwave, and authenticate. That is the whole setup —
the server speaks OAuth 2.0 with dynamic client registration, so there is no key
to copy or config file to hand-edit.
Focused apps
Three single-purpose plugins from ManyMotions (the platform formerly known as Clipwave), each connected to its own hosted MCP server with an interactive panel in Claude:
What you get
Example
Generate three 5-second shots of a ceramic mug on a windowsill — wide, then a slow push-in, then a top-down. Cut them together with 0.4s fades, add the voiceover from
vo.mp3, subtitle it TikTok-style, and export vertical.
Claude reads the model catalogue, picks the right text-to-video id, submits and polls three jobs, creates a project, places six clips across two tracks, sets the transitions, burns the captions, and hands back an MP4 URL.
Requirements
A Clipwave account. Generation spends credits; every
read-only tool (list_models, job_status, and the get_* / list_* family)
is free, and so are the deterministic timeline operations — placing, removing,
reordering, transitions and captions.
Headless use
For CI or server agents with no browser, create a key at
clipwave.io/dashboard/api-keys and send
Authorization: Bearer cw_live_…. There is also a stdio package,
@clipwave/mcp, for clients that
cannot reach a remote server.
Also works with
Cursor, Windsurf, and any MCP-compatible client — the server is plain streamable
HTTP at https://clipwave.io/api/mcp. See clipwave.io/mcp
for the full tool catalogue.
Links
- Tool catalogue and live docs
- REST API docs
- Privacy policy · Terms
- Issues and support: open an issue here, or contact us via the site.
License
MIT — see LICENSE. Clipwave is an independent product; it is not affiliated with or endorsed by Anthropic.
Source: README.md at commit 84a24b2
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
