Ext Ops Panel
Open dashboard
Comparison

renoise vs Hoo MCP — AI Music Production Assistant

renoise is a plugin bundle for AI coding tools published by Renoise. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Hoo MCP — AI Music Production Assistant is an MCP server published by kimny1143. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplacerenoiseHoo MCP — AI Music Production Assistant
Community marketplace arcocodes/renoise-plugins-official Listed
Version: 1.10.0
Forks (GitHub): 17
Stars (GitHub): 60
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.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

renoise vs Hoo MCP — AI Music Production Assistant
FactrenoiseHoo MCP — AI Music Production Assistant
Marketplaces that list it11
Stars (GitHub) (differs)60No figure on GitHub
Forks (GitHub) (differs)17No figure on GitHub
Last release (differs)2026-10-15Not published
Where it runs (differs)Remote server (renoise.ai/api/public/mcp)Remote server (hoo-mcp.glasswerkskimny.workers.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)13Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/arcocodes/renoise-plugins-officialgithub.com/kimny1143/mued_v2
Changes in the last 7 days (differs)50
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)not checked yetResponded 46 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

renoise

In its own words, on Community GitHub marketplaces:

AI video production skills — creative direction, generation, editing, and e-commerce content

Hoo MCP — AI Music Production Assistant

In its own words, on Official MCP Registry:

AI music production assistant — audio profiling, AI mixing sessions, and service inquiries.

How to run each

renoise As a Claude Code plugin

Claude Code
/plugin marketplace add arcocodes/renoise-plugins-official
/plugin install renoise@renoise-plugins-official

Hoo MCP — AI Music Production Assistant As a remote MCP server

Claude Code
claude mcp add --transport http hoo-mcp https://hoo-mcp.glasswerkskimny.workers.dev/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 Hoo MCP — AI Music Production Assistant 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: renoise · What it can do: Hoo MCP — AI Music Production Assistant · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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