EverArt (Archived) vs Clipwave
EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Clipwave is a plugin bundle for AI coding tools published by Clipwave. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  EverArt (Archived) | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:98c2aa1b6231 Forks (GitHub): 11 787 Pulls (Docker Hub): 18 789 Stars (Docker Hub): 3 Stars (GitHub): 91 222 Not marked · First seen |
Not listed |
| Community marketplace clipwave-io/clipwave-plugins | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | EverArt (Archived) | Clipwave |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 222 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 18 789 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 787 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/everart) | Remote server (clipwave.io/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/clipwave-io/clipwave-plugins |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 7 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
EverArt (Archived)
Image generation server using EverArt's API.
Clipwave
Generate video and images, then cut them together on a real multi-track timeline — Claude drives the whole edit and exports an MP4.
How to run each
EverArt (Archived) As a local MCP server: Docker image
claude mcp add --env "EVERART_API_KEY=<YOUR_EVERART_API_KEY>" --transport stdio everart -- docker run -i --rm -e EVERART_API_KEY mcp/everartRequires: EVERART_API_KEY (secret)
Clipwave As a Claude Code plugin
/plugin marketplace add clipwave-io/clipwave-plugins
/plugin install clipwave@clipwaveCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Clipwave has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Clipwave publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Clipwave publish no settings it asks for, so we do not compare settings.
What it can do: EverArt (Archived) · What it can do: Clipwave · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.