copilot-session-dj vs Music Studio
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). Music Studio is an MCP server published by linxule. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (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
| Marketplace |  copilot-session-dj |  Music Studio |
|---|---|---|
| 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: 0.13.0 Downloads/month (npm): 5 673 Downloads/week (npm): 131 Forks (GitHub): 10 Stars (GitHub): 76 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.13.0 Downloads/month (npm): 5 673 Downloads/week (npm): 131 Forks (GitHub): 10 Stars (GitHub): 76 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
| Fact | copilot-session-dj | Music Studio |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 76 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 10 (better) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | AGPL-3.0-or-later | AGPL-3.0-or-later |
| Repository (differs) | github.com/nomhiro/copilot-session-jam | github.com/linxule/mcp-music-studio |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-26 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 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
copilot-session-dj
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.
Music Studio
ABC sheet music + Strudel live coding: songs, videos and live jam sessions in ext-apps widgets.
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.
Music Studio As a remote MCP server
claude mcp add --transport http mcp-music-studio https://music-studio.linxule.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Music Studio has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of copilot-session-dj nor its endpoint list any tools, so we do not compare tools.
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: Music Studio · 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 public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.