AWS Bedrock Data Automation vs VideoVector MCP Server
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). VideoVector MCP Server is an MCP server published by VectorMethods. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  AWS Bedrock Data Automation | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 812 Pulls (Docker Hub): 14 362 Stars (Docker Hub): 0 Stars (GitHub): 9 782 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.2 Downloads/month (npm): 472 Downloads/week (npm): 422 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 | VideoVector MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 782 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 14 362 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 812 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | On your machine (@vectormethods/videovector-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 4, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Analyze documents, images, videos, and audio.
VideoVector MCP Server
Model Context Protocol server for the VectorMethods VideoVector media intelligence API.
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-serverVideoVector MCP Server As a local MCP server: npm package
claude mcp add --env "VIDEOVECTOR_API_KEY=<YOUR_VIDEOVECTOR_API_KEY>" --transport stdio videovector-mcp-server -- npx -y @vectormethods/videovector-mcp-serverRequires: VIDEOVECTOR_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of VideoVector MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS Bedrock Data Automation asks for
AWS_BUCKET_NAMEAWS_PROFILEAWS_REGION
Only VideoVector MCP Server asks for
VIDEOVECTOR_API_KEY (secret)VIDEOVECTOR_BASE_URLVIDEOVECTOR_MAX_RETRIESVIDEOVECTOR_TIMEOUT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS Bedrock Data Automation · What it can do: VideoVector MCP Server · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.