Ext Ops Panel
Open dashboard
Comparison

copilot-session-dj vs Ableton Live MCP Server

copilot-session-dj is a plugin bundle for AI coding tools published by nomhiro. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Ableton Live MCP Server is an MCP server published by wstierhout. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-27. 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
Marketplacecopilot-session-djAbleton Live MCP Server
Copilot CLI: github/awesome-copilot Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.8.1
Downloads/month (PyPI): 2 344
Downloads/week (PyPI): 719
Forks (GitHub): 12
Stars (GitHub): 60
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.8.1
Downloads/month (PyPI): 2 344
Downloads/week (PyPI): 719
Forks (GitHub): 12
Stars (GitHub): 60
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

copilot-session-dj vs Ableton Live MCP Server
Factcopilot-session-djAbleton Live MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)60 (better)
Forks (GitHub) (differs)0 (worse)12 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-server-ableton-live)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)AGPL-3.0-or-laterMIT
Repository (differs)github.com/nomhiro/copilot-session-jamgithub.com/wstierhout/ableton-live-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-262026-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

copilot-session-dj

In its own words, on Copilot CLI: github/awesome-copilot:

A playful, local Strudel soundtrack for the current GitHub Copilot session and its subagents. Includes an English/Japanese DJ Canvas, three synth-only presets, and silent-until-clicked playback with explicit stop controls.

Ableton Live MCP Server

In its own words, on Official MCP Registry:

Control Ableton Live with 156 typed tools for music production and offline .als analysis.

How to run each

copilot-session-dj

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Ableton Live MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio ableton-live-mcp -- uvx mcp-server-ableton-live

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

Neither one's marketplaces publish the settings it asks for.

What it can do: copilot-session-dj · What it can do: Ableton Live MCP Server · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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