Ext Ops Panel
Open dashboard
Comparison

AWS Bedrock Data Automation vs voxflow

AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). voxflow is a plugin bundle for AI coding tools published by VoxFlowStudio. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-16. 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

Where each is published
MarketplaceAWS Bedrock Data Automationvoxflow
Docker MCP Catalog Listed
Version: sha256:ca5c8e3d1bf0
Forks (GitHub): 1 808
Pulls (Docker Hub): 14 353
Stars (Docker Hub): 0
Stars (GitHub): 9 782
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.17.2
Forks (GitHub): 0
Stars (GitHub): 7
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

AWS Bedrock Data Automation vs voxflow
FactAWS Bedrock Data Automationvoxflow
Marketplaces that list it11
Stars (GitHub) (differs)9 782 (better)7 (worse)
Pulls (Docker Hub) (differs)14 353No figure on Docker Hub
Forks (GitHub) (differs)1 808 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-bedrock-data-automation-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)3Not published
Environment variables it asks for (differs)3, secrets among them: 0Not published
Parts of the bundle (differs)Not a bundle6
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/awslabs/mcpgithub.com/voxflowstudio/skills
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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

AWS Bedrock Data Automation

In its own words, on Docker MCP Catalog:

Analyze documents, images, videos, and audio.

voxflow

In its own words, on Claude Code: claude-plugins-community:

AI voice CLI bundled as 5 skills (hub, podcast, transcribe, video, slice). Synthesize speech in 200+ voices across 40+ languages, generate multi-speaker AI podcasts from a topic or URL, transcribe audio/video with word-level timestamps, dub video from SRT subtitles, run end-to-end video translation, and turn long articles into vertical card video reels via Remotion. Backed by a hosted TTS/ASR/LLM/render service with per-user quota (free tier 10K/mo).

How to run each

AWS Bedrock Data Automation As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-bedrock-data-automation -- docker run -i --rm mcp/aws-bedrock-data-automation-mcp-server

voxflow As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install voxflow@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of voxflow publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of voxflow publish no settings it asks for, so we do not compare settings.

What it can do: AWS Bedrock Data Automation · What it can do: voxflow · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built