AWS Bedrock Data Automation vs Clipwave
Clipwave is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Clipwave is a plugin bundle for AI coding tools published by Clipwave. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-21. 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 |  AWS Bedrock Data Automation | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 817 Pulls (Docker Hub): 14 437 Stars (Docker Hub): 0 Stars (GitHub): 9 798 Not marked · First seen |
Not listed |
| Community marketplace clipwave-io/clipwave-plugins | Not listed | Removed on 2026-10-15 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 | AWS Bedrock Data Automation | Clipwaveno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 9 798 | 0 |
| Pulls (Docker Hub) (differs) | 14 437 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 817 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | Remote server (clipwave.io/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/clipwave-io/clipwave-plugins |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
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.
-
Turn footage into finished video: reframing, captions behind the subject, motion graphics, renders.
-
Drive Google Flow from your agent: Veo text-to-video, image-to-video and clip extension, Imagen images, reusable Characters and scene composition.
-
Remotion video creation skills — best practices, animations, audio, captions, 3D, and more for building programmatic videos with React.
-
Create and edit AI videos from chat: plan shots, generate scenes, and export stories and ads.
What each says it does
AWS Bedrock Data Automation
Analyze documents, images, videos, and audio.
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
AWS Bedrock Data Automation As a local MCP server: Docker image
claude mcp add --transport stdio aws-bedrock-data-automation -- docker run -i --rm mcp/aws-bedrock-data-automation-mcp-serverClipwave
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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: AWS Bedrock Data Automation · 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.