The LabelGrid MCP Server lets you manage your LabelGrid music distribution account through natural language. It acts as a typed wrapper over the LabelGrid public API, providing 83 tools across 10 toolsets:
Setup
Get guided instructions to configure your LabelGrid API token (available even before a token is set).
Identity & Account
View your authenticated account profile and revoke API tokens.
Reference Data
Look up genres, languages, contributor roles, instruments, distribution outlets, and territories.
Catalog Management
List, view, create, update, and delete labels, artists, writers, and publishers.
Upload label images and artist photos.
List and view releases, tracks, track files, and download audio via signed URLs.
Release & Track Lifecycle
Create, update, and delete draft releases and tracks.
Validate releases for distribution readiness.
Run Preflight QC quality reports and manage smart-link landing pages.
Add notes to review issues.
Review & Quality
View review issues, quality reports, and Stream Radar flags for artificial streaming detection.
Analytics
Retrieve streaming analytics (streams, listeners, saves, skips, completion rates, geographic breakdowns, etc.) filterable by platform, release, ISRC, UPC, or artist.
Accounting & Royalties
List royalty statements, download CSVs and invoice PDFs.
Browse transactions, royalty breakdowns by track/DSP/territory/period, artificial streaming records, and account balance summaries.
Delivery
Monitor distribution queue status per release and outlet.
View smart-link landing page configurations.
Webhooks
List, create, update, delete, and test webhook subscriptions.
View webhook logs, available event types, and rotate signing secrets.
Distribution (requires explicit opt-in)
Upload finalized track audio (WAV/FLAC/Dolby Atmos) and release artwork.
Upload, update, and delete track licenses.
Distribute releases to stores, take down releases, confirm held releases into review, and request Beatport onboarding for a label.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@LabelGrid MCP Server List my recent releases"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Package | What it is |
The MCP server — 30 consolidated tools over the LabelGrid public API. Published to npm; also ships as the | |
The | |
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. |
Related MCP server: Discogs MCP Server
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'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.
The root package.json is a private workspaces manifest; its scripts fan out to the
packages (npm run build builds @labelgrid/core first, then @labelgrid/mcp and
@labelgrid/cli; npm test runs each package's suite). Contributors work from the repo
root: packages/core is the shared client, packages/mcp the MCP server, packages/cli
the command-line tool — the two products are thin adapters over core.
Each package has its own tsconfig.json extending the shared tsconfig.base.json
(no TypeScript project references — the explicit root build chain keeps ordering correct and
simple). @labelgrid/mcp imports @labelgrid/core through 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/core to 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.
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 repoThe 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Official MCP server for Lovable, the AI-powered full-stack app builder.
MCP server for Producer/Riffusion AI music generation
GibsonAI MCP server: manage your databases with natural language
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/labelgrid/labelgrid-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server