AWS Bedrock Data Automation vs autosound-tuning
autosound-tuning is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). autosound-tuning is a plugin bundle for AI coding tools published by ayukhno. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-27. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 830 Pulls (Docker Hub): 14 665 Stars (Docker Hub): 0 Stars (GitHub): 9 835 Not marked · First seen |
Not listed |
| Community marketplace ayukhno/autosound-tuning-skill | Not listed | Removed on 2026-10-26 Version: 3.2.0 Forks (GitHub): 3 Stars (GitHub): 10 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 | autosound-tuningno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 9 835 | 10 |
| Pulls (Docker Hub) (differs) | 14 665 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 830 | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | Not published |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence (differs) | Apache-2.0 | CC-BY-SA-4.0 |
| Repository (differs) | github.com/awslabs/mcp | github.com/ayukhno/autosound-tuning-skill |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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 autosound-tuning
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
AI audio engineering system that turns Claude into a professional mix and mastering engineer. Point it at stems or a full mix, give it a reference track you want to sound like…
-
Audio perception for AI agents: measure, see, compare, edit and synthesize sound locally.
-
Let your assistant see your recording's spectrogram, box the noise, and heal only that.
-
Enables AI assistants to control REAPER for mixing, mastering, MIDI and music production.
-
Bridge between Ableton Live and AI. Inspect, analyze audio, and control mixing via MCP.
-
Audio and video tools for your AI assistant: remove noise, enhance voices, transcribe, and more.
What each says it does
AWS Bedrock Data Automation
Analyze documents, images, videos, and audio.
autosound-tuning
Tune a car-audio DSP with REW — intake → crossovers → time alignment → phase → EQ → imaging → taste voicing, via a Generator-Critic-Arbiter review loop. Any car, any DSP. Bundles the review-loop method (independent multi-AI review + anti-anchoring).
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-server
autosound-tuning
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 autosound-tuning publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of autosound-tuning publish no settings it asks for, so we do not compare settings.
What it can do: AWS Bedrock Data Automation · What it can do: autosound-tuning · 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.