Audio vs AudioKit
Audio is an MCP server published by audiojs. Marketplaces we read that list it: 1 (Official MCP Registry). AudioKit is an MCP server published by epsilon-records. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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 |  Audio | |
|---|---|---|
| Official MCP Registry | Listed Version: 2.10.0 Downloads/month (npm): 1 539 Downloads/week (npm): 685 Forks (GitHub): 11 Stars (GitHub): 336 Not marked · First seen |
Listed Version: 0.1.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
| Fact | Audio | AudioKit |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 336 | No figure on GitHub |
| Forks (GitHub) (differs) | 11 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (audio) | Remote server (api.audiokit.ai/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/audiojs/audio | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-13 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 14 h ago, requires authentication |
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
Audio
Edit, analyze and convert audio: loudness, spec checks, denoise, EQ, cuts, BPM, key. No ffmpeg.
AudioKit
Audio analysis and production jobs: BPM, key, fingerprint, tags, stems, cleanup, mastering.
How to run each
Audio As a local MCP server: npm package
claude mcp add --transport stdio audio -- npx -y audio --mcpAudioKit As a remote MCP server
claude mcp add --transport http audiokit https://api.audiokit.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only AudioKit has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Audio · What it can do: AudioKit · 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.