mcpField
L
labelgrid-mcp

labelgrid-mcp

Local
labelgrid.comBusiness & Marketing4Updated 4w ago
RepositoryVisit website

About labelgrid-mcp

labelgrid-mcp is the official MCP server for LabelGrid's public API, with 30 tools covering music catalog and release operations. It is part of a workspace that also provides a CLI and a shared API client.

Key features

  1. 01Manage music catalog and releases
  2. 02Work with files and distribution
  3. 03Access analytics and royalties
  4. 04Manage webhooks
  5. 05Use 30 consolidated API tools

Use cases

  1. 01Manage a music catalog through an MCP client
  2. 02Handle release and distribution tasks
  3. 03Review analytics and royalty information

MCP support

The @labelgrid/mcp package exposes 30 tools over the LabelGrid public API to MCP clients. The project also includes a CLI for the same API surface.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "labelgrid-labelgrid": {
      "command": "npx",
      "args": [
        "-y",
        "@labelgrid/mcp"
      ],
      "env": {
        "LABELGRID_API_TOKEN": "<LABELGRID_API_TOKEN>",
        "LABELGRID_API_URL": "<LABELGRID_API_URL>",
        "LABELGRID_ENABLE_WRITES": "<LABELGRID_ENABLE_WRITES>",
        "LABELGRID_ENABLE_FULL_WRITES": "<LABELGRID_ENABLE_FULL_WRITES>",
        "LABELGRID_FULL_WRITES_ACK": "<LABELGRID_FULL_WRITES_ACK>",
        "LABELGRID_TOOLSETS": "<LABELGRID_TOOLSETS>",
        "LABELGRID_READ_ONLY": "<LABELGRID_READ_ONLY>"
      }
    }
  }
}
Run commandnpx -y @labelgrid/mcp
Environment variables to set
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_WRITESEnable safe writes (create/update drafts, labels, artists, and similar). Enabled by default; set to false for read-only.
LABELGRID_ENABLE_FULL_WRITESEnable full writes (distribution, takedowns, immutable uploads). Disabled by default; also requires LABELGRID_FULL_WRITES_ACK.
LABELGRID_FULL_WRITES_ACKMust equal the exact acknowledgment sentence (see the README safety section) to arm full writes.
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.
LABELGRID_READ_ONLYForce reads only; overrides both write flags. Defaults to false.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@labelgrid/mcp0.4.0

Tools

29

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project README

LabelGrid MCP — workspace

npm version CI LabelGrid MCP server

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

PackageWhat it is
@labelgrid/mcpThe 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/cliThe 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/coreThe 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.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.

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

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.