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.

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