Manage music catalogs, releases, analytics, and distribution through an AI-driven interface.
Also known as labelgrid/labelgrid-mcp, @labelgrid/mcp
- Stars
- 4
- Tools
- —
- Downloads, 30 days
- 873
- Latest version
- 0.4.0
- Last commit
- Nov 10, 2026
- License
- MIT
What is LabelGrid MCP?
LabelGrid manages music catalogs, releases, analytics, and distribution through an AI-driven interface.
Summary generated from the project's README
About LabelGrid MCP server
LabelGrid MCP provides a specialized interface for managing music catalogs, releases, and distribution through an AI client. It connects to the LabelGrid public API to offer thirty consolidated tools that allow users to handle everything from catalog searches to royalty tracking. This server is designed for developers and music professionals who want to integrate music management workflows directly into their AI-driven environments.
Users can set up the server via npm or use the labelgrid.mcpb one-click bundle for Claude Desktop. To function, the system requires a LabelGrid API token for authentication. The server operates as an adapter over the core API, providing structured access to files, analytics, and webhooks. It is built to support complex workflows like the full release lifecycle, including drafting releases, uploading audio and artwork, and tracking delivery status.
What you can do with it
- 1Manage the release lifecycleAn agent can draft a release, upload necessary audio and artwork files, and then distribute the content.
- 2Search music catalogsA developer can use the tools to find specific releases within a music catalog using JSON output for data processing.
- 3Monitor music analyticsUsers can access data regarding royalties and distribution performance through the integrated API tools.
Written from the project's README. Every use case is checked against a quote from it.
How to install LabelGrid MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall LabelGrid MCP in Claude Code
$ claude mcp add --env 'LABELGRID_API_TOKEN=<YOUR_LABELGRID_API_TOKEN>' labelgrid-mcp -- npx -y @labelgrid/mcpInstall LabelGrid MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"labelgrid-mcp": {
"command": "npx",
"args": [
"-y",
"@labelgrid/mcp"
],
"env": {
"LABELGRID_API_TOKEN": "<YOUR_LABELGRID_API_TOKEN>"
}
}
}
}Install LabelGrid MCP in VS Code
.vscode/mcp.json
{
"servers": {
"labelgrid-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@labelgrid/mcp"
],
"env": {
"LABELGRID_API_TOKEN": "<YOUR_LABELGRID_API_TOKEN>"
}
}
}
}Install LabelGrid MCP in VS Code CLI
$ code --add-mcp '{"name":"labelgrid-mcp","type":"stdio","command":"npx","args":["-y","@labelgrid/mcp"],"env":{"LABELGRID_API_TOKEN":"<YOUR_LABELGRID_API_TOKEN>"}}'Install LabelGrid MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"labelgrid-mcp": {
"command": "npx",
"args": [
"-y",
"@labelgrid/mcp"
],
"env": {
"LABELGRID_API_TOKEN": "<YOUR_LABELGRID_API_TOKEN>"
}
}
}
}Install LabelGrid MCP in Codex
$ codex mcp add labelgrid-mcp --env 'LABELGRID_API_TOKEN=<YOUR_LABELGRID_API_TOKEN>' -- npx -y @labelgrid/mcpInstall LabelGrid MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.labelgrid-mcp] command = "npx" args = ["-y", "@labelgrid/mcp"] [mcp_servers.labelgrid-mcp.env] LABELGRID_API_TOKEN = "<YOUR_LABELGRID_API_TOKEN>"
Install LabelGrid MCP in Gemini CLI
$ gemini mcp add -s user -e 'LABELGRID_API_TOKEN=<YOUR_LABELGRID_API_TOKEN>' labelgrid-mcp npx -- -y @labelgrid/mcpInstall LabelGrid MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"labelgrid-mcp": {
"command": "npx",
"args": [
"-y",
"@labelgrid/mcp"
],
"env": {
"LABELGRID_API_TOKEN": "<YOUR_LABELGRID_API_TOKEN>"
}
}
}
}Configuration
LABELGRID_API_TOKENSecretYour LabelGrid API token. Create one in your dashboard under Profile → API Tokens. Without it the server starts in setup mode and walks you through creating one.
LABELGRID_API_URLOverride the API base URL. Defaults to the production API.
LABELGRID_ENABLE_FULL_WRITESEnable full writes (distribution, takedowns, immutable uploads). Disabled by default; also requires LABELGRID_FULL_WRITES_ACK.
LABELGRID_ENABLE_WRITESEnable safe writes (create/update drafts, labels, artists, and similar). Enabled by default; set to false for read-only.
LABELGRID_FULL_WRITES_ACKMust equal the exact acknowledgment sentence (see the README safety section) to arm full writes.
LABELGRID_READ_ONLYForce reads only; overrides both write flags. Defaults to false.
LABELGRID_TOOLSETSComma-separated subset of toolsets to expose (account, reference, catalog, releases, insights, finance, webhooks, distribution; pre-0.3.0 names are accepted as aliases). Defaults to all except webhooks, which must be named explicitly to enable.
| Name | Description | |
|---|---|---|
| LABELGRID_API_TOKEN | Your LabelGrid API token. Create one in your dashboard under Profile → API Tokens. Without it the server starts in setup mode and walks you through creating one. | Secret |
| LABELGRID_API_URL | Override the API base URL. Defaults to the production API. | |
| LABELGRID_ENABLE_FULL_WRITES | Enable full writes (distribution, takedowns, immutable uploads). Disabled by default; also requires LABELGRID_FULL_WRITES_ACK. | |
| LABELGRID_ENABLE_WRITES | Enable safe writes (create/update drafts, labels, artists, and similar). Enabled by default; set to false for read-only. | |
| LABELGRID_FULL_WRITES_ACK | Must equal the exact acknowledgment sentence (see the README safety section) to arm full writes. | |
| LABELGRID_READ_ONLY | Force reads only; overrides both write flags. Defaults to false. | |
| LABELGRID_TOOLSETS | Comma-separated subset of toolsets to expose (account, reference, catalog, releases, insights, finance, webhooks, distribution; pre-0.3.0 names are accepted as aliases). Defaults to all except webhooks, which must be named explicitly to enable. |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubLabelGrid MCP — workspace
The official LabelGrid tooling for the LabelGrid public API, organised as an npm workspace.
Looking for the MCP server docs? They live in
packages/mcp/README.md — installation for Claude Desktop / Cursor /
any MCP client, the full tool reference, safety gating, and configuration.
Packages
| Package | What it is |
|---|---|
@labelgrid/mcp |
The MCP server — 30 consolidated tools over the LabelGrid public API. Published to npm; also ships as the labelgrid.mcpb one-click bundle for Claude Desktop. |
@labelgrid/cli |
The labelgrid command-line tool — the same API surface for terminals and scripts: catalog, releases, files, analytics, royalties, webhooks, and distribution, with --json output for pipelines. |
@labelgrid/core |
The shared API client: HTTP transport with structured errors, presigned-URL uploads, content-type allowlists, the catalog-entity registry, and redacting logging. Used by every LabelGrid tool built on the public API. |
Command-line tool
Full docs (auth setup, every command group, scripting, safety model) live in
packages/cli/README.md. Quickstart:
npm install -g @labelgrid/cli # Node 20+; installs the `labelgrid` command
export LABELGRID_API_TOKEN=... # or run `labelgrid auth login`
labelgrid auth whoami # verify the token
labelgrid catalog search --type release --json | jq '.data[].id'
Agent skill
skills/labelgrid-release/SKILL.md is an agent
skill for the full release lifecycle — draft a release and its tracks, upload audio and
artwork, validate, review, distribute, and track delivery — with the exact MCP tool and
CLI command for each step and guidance on which vehicle fits. Point an agent at the file,
or drop it into your assistant's skills directory, to teach it the end-to-end LabelGrid
release flow.
Layout & build arrangement
- The root
package.jsonis a private workspaces manifest; its scripts fan out to the packages (npm run buildbuilds@labelgrid/corefirst, then@labelgrid/mcpand@labelgrid/cli;npm testruns each package's suite). Contributors work from the repo root:packages/coreis the shared client,packages/mcpthe MCP server,packages/clithe command-line tool — the two products are thin adapters over core. - Each package has its own
tsconfig.jsonextending the sharedtsconfig.base.json(no TypeScript project references — the explicit root build chain keeps ordering correct and simple).@labelgrid/mcpimports@labelgrid/corethrough the workspace link and compiles against its built declarations. - Unit tests run per package via each package's
vitest.config.ts. The MCP package aliases@labelgrid/coreto the sibling package's TypeScript source, so running tests never requires a prior core build. - Repo-wide checks live in
scripts/and run from the root:npm run lint,npm run leak-guard,npm run check-coverage,npm run gen-docs,npm run measure-tokens.
Development
npm ci # install the whole workspace
npm run build # build core, then mcp and cli
npm test # unit suites for every package
npm run lint # biome over the repo
The MCP server binary after a build: node packages/mcp/dist/index.js (or npm start).
The CLI binary after a build: node packages/cli/dist/index.js.
License
LabelGrid MCP questions
How do I add LabelGrid MCP to Claude Code?
Run claude mcp add --env 'LABELGRID_API_TOKEN=<YOUR_LABELGRID_API_TOKEN>' labelgrid-mcp -- npx -y @labelgrid/mcp in your terminal. Add --scope user to make it available in every project.
How do I add LabelGrid MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I authenticate with the LabelGrid CLI?
You can authenticate by exporting a LABELGRID_API_TOKEN or by running the command 'labelgrid auth login'.