Clipwave vs Clypmint
Clipwave is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
Clipwave is a plugin bundle for AI coding tools published by Clipwave. No marketplace we read lists it any more. Clypmint is an MCP server published by clypmint.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Clypmint | |
|---|---|---|
| Community marketplace clipwave-io/clipwave-plugins | Removed on 2026-10-15 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.1 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Clipwaveno longer listed · | Clypmint |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-23 |
| Where it runs (differs) | Remote server (clipwave.io/api/mcp) | Remote server (clypmint.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/clipwave-io/clipwave-plugins | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 303 (15 h ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Clipwave
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Local video studio for your coding agent: scenes, voice, music and captions, on your machine.
-
Professional AI video creation toolkit for Claude Code. Edit videos, generate video content, and enhance images using natural language.
-
Edição de vídeo vertical com o Claude Code: 9 skills (porta de entrada, cortes, motion, colagem em camadas, curiosidade histórica, explicador Vox, documentário de arquivo, time de…
-
Video editing skills, motion design prompts and studio concepts for creators who edit with Claude.
-
Edit your own clips into finished short-form videos from a brief or a reference video.
-
Drive Google Flow from your agent: Veo text-to-video, image-to-video and clip extension, Imagen images, reusable Characters and scene composition.
What each says it does
Clipwave
Generate video and images, then cut them together on a real multi-track timeline — Claude drives the whole edit and exports an MP4.
Clypmint
Edit videos with AI: cuts, captions, B-roll and motion in a style you pick or copy from any video.
How to run each
Clipwave
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Clypmint As a remote MCP server
claude mcp add --transport http clypmint https://clypmint.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Clypmint has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of Clipwave nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Clipwave · What it can do: Clypmint · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.