English Français العربية

Lacuna Music

Official registry Developer tools

Generate AI music via the Lacuna Music API from MCP clients like Claude Desktop & Code.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http lacuna-music 'https://www.lacuna.fm/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "lacuna-music": {
            "type": "http",
            "url": "https://www.lacuna.fm/mcp"
        }
    }
}
NPM package lacuna-mcp
Claude Code 
claude mcp add lacuna-music -e 'LACUNA_API_KEY=<your lacuna_api_key>' -e 'LACUNA_BASE_URL=<LACUNA_BASE_URL>' -- npx -y lacuna-mcp@0.3.4
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "lacuna-music": {
            "command": "npx",
            "args": [
                "-y",
                "lacuna-mcp@0.3.4"
            ],
            "env": {
                "LACUNA_API_KEY": "<your lacuna_api_key>",
                "LACUNA_BASE_URL": "<LACUNA_BASE_URL>"
            }
        }
    }
}

Environment variables

  • LACUNA_API_KEY required secret Lacuna API key from https://www.lacuna.fm/profile/api
  • LACUNA_BASE_URL Override the API base URL (optional).

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Lacuna developer tools
  2. Repository layout
  3. Development
  4. Releasing
  5. Distributing the skill
  6. License

Lacuna developer tools

Open-source SDK, CLI, MCP server, and Agent Skill for the Lacuna Music API. Generate AI music programmatically from any Node 18+ runtime, your shell, an MCP-compatible client, or an AI coding agent that supports the Agent Skills standard.

SurfaceInstallUse case
lacuna-sdknpm install lacuna-sdkTypeScript / JavaScript SDK with webhook verification.
lacuna-toolkitnpx lacuna-toolkitCommand-line interface for one-off generation, scripting, CI.
lacuna-mcpnpx lacuna-mcpModel Context Protocol server for Claude Desktop, Claude Code, Cursor, etc.
lacuna-music skillnpx skills add JOYLINK-LTD/lacuna-toolkitAgent Skill for Claude Code, Codex CLI, Cursor, and other tools that follow the SKILL.md standard.

The three npm packages are released together and share the same API surface. The skill is markdown-only and tracks the latest published packages.

Repository layout

.
├── packages/
│   ├── sdk/                   →  npm: lacuna-sdk
│   ├── cli/                   →  npm: lacuna-toolkit
│   └── mcp/                   →  npm: lacuna-mcp
├── skills/
│   └── lacuna-music/SKILL.md  →  Agent Skill (skills.sh, skillsmp.com, etc.)
├── pnpm-workspace.yaml
├── tsconfig.base.json
└── package.json

This is a pnpm workspace. The CLI and MCP server depend on the SDK via workspace:*, which is rewritten to a real version range on publish. The skill is plain markdown and is not part of the workspace.

Development

pnpm install            # install all workspace deps
pnpm -r run build       # build every package
pnpm -r run typecheck   # typecheck every package
pnpm --filter lacuna-mcp run dev  # iterate on a single package

The SDK must be built before pnpm -r run typecheck can resolve the CLI/MCP packages' types. pnpm -r run build handles dependency order automatically.

Releasing

Each package versions independently from packages/<pkg>/package.json. Bump versions in lockstep, build, then publish:

# bump the version in all three package.jsons + packages/mcp/server.json
# (packages/sdk/src/version.ts is injected from package.json at build time — do not hand-edit)
pnpm -r run build
pnpm --filter lacuna-sdk publish --access public
pnpm --filter lacuna-toolkit publish --access public
pnpm --filter lacuna-mcp publish --access public

workspace:* references in dependencies are rewritten to the published version automatically (pnpm handles this).

Distributing the skill

The skill at skills/lacuna-music/ follows the Agent Skills open standard, so it works with Claude Code, Codex CLI, Cursor, and any other tool that loads SKILL.md files.

There is no submission step for skill marketplaces — they index public GitHub repos automatically:

  • skills.sh (Vercel Labs) ranks skills by anonymous install telemetry. Once the repo is public, anyone can install with npx skills add JOYLINK-LTD/lacuna-toolkit, and installs feed the leaderboard. The CLI auto-discovers SKILL.md files under skills/<name>/.
  • skillsmp.com and claudeskills.info crawl public GitHub repos that contain SKILL.md and a minimum of 2 stars.
  • The official anthropics/skills repo accepts community-contributed skills via PR if you want a canonical listing.

To verify discovery locally:

npx skills add JOYLINK-LTD/lacuna-toolkit

This installs lacuna-music into ~/.claude/skills/lacuna-music/ (and the equivalent for other agents). Edits to skills/lacuna-music/SKILL.md show up on the next skills add.

License

MIT © Louis Tsang

Frequently asked questions

What is Lacuna Music?

Generate AI music via the Lacuna Music API from MCP clients like Claude Desktop & Code.

How do I install Lacuna Music?

It runs as a remote server. In Claude Code: claude mcp add --transport http lacuna-music 'https://www.lacuna.fm/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Lacuna Music need an API key?

Yes. It expects LACUNA_API_KEY, which you set in its configuration.

Is Lacuna Music open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Lacuna Music?

It is published by JOYLINK-LTD. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.