Ext Ops Panel
Open dashboard
Comparison

AWS Bedrock Data Automation vs ScribeToAny

AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). ScribeToAny is an MCP server published by scribetoany.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 AutomationScribeToAny
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
Official MCP Registry Not listed Listed
Version: 1.0.0
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

AWS Bedrock Data Automation vs ScribeToAny
FactAWS Bedrock Data AutomationScribeToAny
Marketplaces that list it11
Stars (GitHub) (differs)9 798No figure on GitHub
Pulls (Docker Hub) (differs)14 437No figure on Docker Hub
Forks (GitHub) (differs)1 817No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-bedrock-data-automation-mcp-server)Remote server (scribetoany.com/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks for (differs)3, secrets among them: 0Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-18
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

ScribeToAny

In its own words, on Official MCP Registry:

Transcribe audio and video into timestamped transcripts, and search and read your transcripts.

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

ScribeToAny As a remote MCP server

Claude Code
claude mcp add --transport http scribetoany https://scribetoany.com/api/mcp

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

Tools each declares

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

Settings each asks for

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

What it can do: AWS Bedrock Data Automation · What it can do: ScribeToAny · 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.

Where the data comes from: how the catalog is built