io.github.AetherWave-Studio/aetherwave-mcp vs MirrorEdge AI: Waves
io.github.AetherWave-Studio/aetherwave-mcp is an MCP server published by AetherWave-Studio. Marketplaces we read that list it: 1 (Official MCP Registry). MirrorEdge AI: Waves is an MCP server published by MirrorEdgeAI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  io.github.AetherWave-Studio/aetherwave-mcp |  MirrorEdge AI: Waves |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.6 Downloads/month (npm): 630 Downloads/week (npm): 98 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 0.5.3 Downloads/month (npm): 127 Downloads/week (npm): 23 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 | io.github.AetherWave-Studio/aetherwave-mcp | MirrorEdge AI: Waves |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@aetherwave-studio/mcp) | On your machine (waves-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/aetherwave-studio/aetherwave-mcp | github.com/mirroredgeai/waves-claude |
| 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
io.github.AetherWave-Studio/aetherwave-mcp
Music, image, video and audio generation across top AI providers - one key, one credit pool.
MirrorEdge AI: Waves
Let your assistant see your recording's spectrogram, box the noise, and heal only that.
How to run each
io.github.AetherWave-Studio/aetherwave-mcp As a local MCP server: npm package
claude mcp add --env "AETHERWAVE_API_KEY=<YOUR_AETHERWAVE_API_KEY>" --transport stdio aetherwave-mcp -- npx -y @aetherwave-studio/mcpRequires: AETHERWAVE_API_KEY (secret)
MirrorEdge AI: Waves As a local MCP server: npm package
claude mcp add --transport stdio waves -- npx -y waves-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.AetherWave-Studio/aetherwave-mcp asks for
AETHERWAVE_API_KEY (secret)
Only MirrorEdge AI: Waves asks for
WAVES_EXECUTABLE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.AetherWave-Studio/aetherwave-mcp · What it can do: MirrorEdge AI: Waves · Compare two other plugins
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.