Ext Ops Panel
Open dashboard
Comparison

decibel-tools-plugin vs Audionaut

decibel-tools-plugin is a plugin bundle for AI coding tools published by decibelsystems. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Audionaut is an MCP server published by kvoltmer. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacedecibel-tools-pluginAudionaut
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Downloads/month (npm): 515
Downloads/week (npm): 103
Forks (GitHub): 14
Stars (GitHub): 252
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

decibel-tools-plugin vs Audionaut
Factdecibel-tools-pluginAudionaut
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)252 (better)
Forks (GitHub) (differs)0 (worse)14 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@decibelsystems/tools)On your machine (audionaut-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/decibelsystems/tools-plugingithub.com/kvoltmer/audionaut
Changes in the last 7 days00
First seen2026-10-112026-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

decibel-tools-plugin

In its own words, on Claude Code: claude-plugins-community:

Auto-configures the Decibel MCP server for Claude Code. The Tools plugin installs the MCP connection for you so Claude Code can access Decibel project intelligence, workflows, architecture context, and other MCP-powered capabilities without manual setup.

Audionaut

In its own words, on Official MCP Registry:

Edit Audionaut multitrack audio projects: cut, arrange, fade, analyse, auto-edit, export

How to run each

decibel-tools-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install decibel-tools-plugin@claude-community

Audionaut As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio audionaut -- npx -y audionaut-mcp

Commands 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

The marketplaces of decibel-tools-plugin publish no settings it asks for, so we do not compare settings.

What it can do: decibel-tools-plugin · What it can do: Audionaut · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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