Ext Ops Panel
Open dashboard
Comparison

phantom vs StemLab — timing and loops for Shorts

phantom is a plugin bundle for AI coding tools published by fadelabs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). StemLab — timing and loops for Shorts is an MCP server published by kieransimkin. 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
MarketplacephantomStemLab — timing and loops for Shorts
Claude Code: claude-plugins-community Listed
Version: 1.3.0
Forks (GitHub): 1
Stars (GitHub): 39
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.1
Downloads/month (PyPI): 781
Downloads/week (PyPI): 798
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

phantom vs StemLab — timing and loops for Shorts
FactphantomStemLab — timing and loops for Shorts
Marketplaces that list it11
Stars (GitHub) (differs)39 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleOn your machine (danceflow-stemlab)
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)5Not a bundle
Licence (differs)AGPL-3.0-or-laterNot stated
Repository (differs)github.com/fadelabs/phantomgithub.com/kieransimkin/stemlab
Changes in the last 7 days (differs)01
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

phantom

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

AI audio engineering system that turns Claude into a professional mix and mastering engineer. Point it at stems or a full mix, give it a reference track you want to sound like, and it handles the rest: diagnostics, session setup, mixing, effects, and mastering in Reaper. Backed by real-time spectral, loudness, dynamics, stereo, and phase analysis via the Phantom MCP server. 5 domain expert skills work together as a complete audio production pipeline: analyze first, set up the DAW, mix with measurement-backed decisions, add creative effects, and master to streaming specs.

StemLab — timing and loops for Shorts

In its own words, on Official MCP Registry:

Music and stem analysis, timing and loopable Shorts. https://kieransimkin.co.uk/

How to run each

phantom As a Claude Code plugin

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

StemLab — timing and loops for Shorts As a local MCP server: PyPI package

Claude Code
claude mcp add --env "STEMLAB_CODEX_WORKSPACE=<YOUR_STEMLAB_CODEX_WORKSPACE>" --transport stdio stemlab -- uvx --with "mcp>=2.2,<3" danceflow-stemlab serve

Requires: STEMLAB_CODEX_WORKSPACE

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 phantom publish no settings it asks for, so we do not compare settings.

What it can do: phantom · What it can do: StemLab — timing and loops for Shorts · 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