musiccontext vs Lacuna Music
musiccontext is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
musiccontext is a plugin bundle for AI coding tools published by MusicContext contributors. No marketplace we read lists it any more. Lacuna Music is an MCP server published by JOYLINK-LTD. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Lacuna Music | |
|---|---|---|
| Community marketplace aagam17/musiccontext | Removed on 2026-10-16 Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.4 Downloads/month (npm): 174 Downloads/week (npm): 68 Forks (GitHub): 2 Stars (GitHub): 5 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 | musiccontextno longer listed · | Lacuna Music |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 5 |
| Forks (GitHub) (differs) | 1 | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (www.lacuna.fm/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/aagam17/musiccontext | github.com/joylink-ltd/lacuna-toolkit |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of musiccontext
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
AI story development, screenplay editing, review, media, and export tools for BeatBandit projects.
-
Generate full songs with vocals, instrumentals and sound effects from text.
-
Doseedo: Film Scoring, AI Instruments, Sound Effects & Stems
Score video & make music as an agent: 50+ AI instruments play your MIDI, audio, stems, Logic/Ableton
-
Official BizMuse MCP for complete AI music videos from audio and 1-7 reference images.
-
AI music generation workflow for Suno - album concepts, lyrics, prompts, mastering, release
-
Freebeat MCP server for AI music videos, effects, and media uploads.
What each says it does
musiccontext
Music direction for AI agents: video -> story -> music direction -> soundtrack -> sync.
Lacuna Music
Generate AI music via the Lacuna Music API from MCP clients like Claude Desktop & Code.
How to run each
musiccontext
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Lacuna Music As a remote MCP server
claude mcp add --transport http lacuna-mcp https://www.lacuna.fm/mcpRequires: LACUNA_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Lacuna Music 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
The marketplaces of musiccontext publish no settings it asks for, so we do not compare settings.
What it can do: musiccontext · What it can do: Lacuna Music · 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.