English Français العربية

io.github.labelgrid/labelgrid-mcp

Registre officiel Marketing et ventes

Official LabelGrid MCP server — manage your music catalog, releases, analytics and distribution.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @labelgrid/mcp
Claude Code 
claude mcp add labelgrid-mcp -e 'LABELGRID_API_TOKEN=<your labelgrid_api_token>' -e 'LABELGRID_API_URL=<LABELGRID_API_URL>' -e 'LABELGRID_ENABLE_WRITES=<LABELGRID_ENABLE_WRITES>' -e 'LABELGRID_ENABLE_FULL_WRITES=<LABELGRID_ENABLE_FULL_WRITES>' -e 'LABELGRID_FULL_WRITES_ACK=<LABELGRID_FULL_WRITES_ACK>' -e 'LABELGRID_TOOLSETS=<LABELGRID_TOOLSETS>' -e 'LABELGRID_READ_ONLY=<LABELGRID_READ_ONLY>' -- npx -y @labelgrid/mcp@0.4.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "labelgrid-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@labelgrid/mcp@0.4.0"
            ],
            "env": {
                "LABELGRID_API_TOKEN": "<your 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>"
            }
        }
    }
}

Variables d'environnement

  • LABELGRID_API_TOKEN secret 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.
  • LABELGRID_API_URL Override the API base URL. Defaults to the production API.
  • LABELGRID_ENABLE_WRITES Enable safe writes (create/update drafts, labels, artists, and similar). Enabled by default; set to false for read-only.
  • LABELGRID_ENABLE_FULL_WRITES Enable full writes (distribution, takedowns, immutable uploads). Disabled by default; also requires LABELGRID_FULL_WRITES_ACK.
  • LABELGRID_FULL_WRITES_ACK Must equal the exact acknowledgment sentence (see the README safety section) to arm full writes.
  • 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.
  • LABELGRID_READ_ONLY Force reads only; overrides both write flags. Defaults to false.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. LabelGrid MCP — workspace
  2. Packages
  3. Command-line tool
  4. Agent skill
  5. Layout & build arrangement
  6. Development
  7. License

LabelGrid 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

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

Questions fréquentes

Qu'est-ce que io.github.labelgrid/labelgrid-mcp ?

Official LabelGrid MCP server — manage your music catalog, releases, analytics and distribution.

Comment installer io.github.labelgrid/labelgrid-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add labelgrid-mcp -e 'LABELGRID_API_TOKEN=<your labelgrid_api_token>' -e 'LABELGRID_API_URL=<LABELGRID_API_URL>' -e 'LABELGRID_ENABLE_WRITES=<LABELGRID_ENABLE_WRITES>' -e 'LABELGRID_ENABLE_FULL_WRITES=<LABELGRID_ENABLE_FULL_WRITES>' -e 'LABELGRID_FULL_WRITES_ACK=<LABELGRID_FULL_WRITES_ACK>' -e 'LABELGRID_TOOLSETS=<LABELGRID_TOOLSETS>' -e 'LABELGRID_READ_ONLY=<LABELGRID_READ_ONLY>' -- npx -y @labelgrid/mcp@0.4.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.labelgrid/labelgrid-mcp ?

Oui. Il attend LABELGRID_API_TOKEN, à renseigner dans sa configuration.

io.github.labelgrid/labelgrid-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.labelgrid/labelgrid-mcp ?

Il est publié par labelgrid. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.