AWS Bedrock Data Automation vs HanoLab Voice Conversion
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). HanoLab Voice Conversion is an MCP server published by obrr-hhx. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  HanoLab Voice Conversion |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 830 Pulls (Docker Hub): 14 671 Stars (Docker Hub): 0 Stars (GitHub): 9 835 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 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 | HanoLab Voice Conversion |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 835 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 14 671 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 830 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | Remote server (hanolab.com/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 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/hanolab-ai/hanolab-integrations |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 23 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
AWS Bedrock Data Automation
Analyze documents, images, videos, and audio.
HanoLab Voice Conversion
Convert uploaded speech or singing with your saved HanoLab voices, using OAuth and credit quotes.
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-serverHanoLab Voice Conversion As a remote MCP server
claude mcp add --transport http hanolab https://hanolab.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only HanoLab Voice Conversion has a remote endpoint we check. How we check endpoints
Tools each declares
Only AWS Bedrock Data Automation has
analyzeassetgetprojectdetailsgetprojects
Only HanoLab Voice Conversion has
convert_voicecreate_upload_linkget_creditsget_profileget_tasklist_audiolist_conversionslist_voicesprepare_voice_conversion
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (HanoLab Voice Conversion as of 2026-10-19). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of HanoLab Voice Conversion publish no settings it asks for, so we do not compare settings.
What it can do: AWS Bedrock Data Automation · What it can do: HanoLab Voice Conversion · 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.