Ext Ops Panel
Open dashboard
Comparison

Compeller vs io.github.dreamrec/livepilot

Compeller is an MCP server published by compeller.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.dreamrec/livepilot is an MCP server published by dreamrec. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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
MarketplaceCompellerio.github.dreamrec/livepilot
Official MCP Registry Listed
Version: 0.5.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.10.4
Downloads/month (npm): 1 975
Downloads/week (npm): 263
Forks (GitHub): 20
Stars (GitHub): 88
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.30.0
Downloads/month (npm): 1 975
Downloads/week (npm): 263
Forks (GitHub): 20
Stars (GitHub): 88
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

Compeller vs io.github.dreamrec/livepilot
FactCompellerio.github.dreamrec/livepilot
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)1 (worse)88 (better)
Forks (GitHub) (differs)0 (worse)20 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (compeller.ai/api/mcp)On your machine (livepilot)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle24
Licence (differs)Not statedBSL-1.1
Repository (differs)github.com/compellerai/compeller-mcpgithub.com/dreamrec/livepilot
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days agono remote endpoint we check

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

Compeller

In its own words, on Official MCP Registry:

Create and track AI music videos and audio-reactive visuals from songs.

io.github.dreamrec/livepilot

In its own words, on Official MCP Registry:

317-tool agentic MCP production system for Ableton Live 12 — device atlas, sample engine, composer

How to run each

Compeller As a remote MCP server

Claude Code
claude mcp add --transport http compel https://compeller.ai/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>" --header "X-API-Token: <YOUR_X_API_TOKEN>"

Requires: Authorization header, X-API-Token header

io.github.dreamrec/livepilot As a local MCP server: npm package

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Compeller 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: Compeller · What it can do: io.github.dreamrec/livepilot · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.

Where the data comes from: how the catalog is built