# labelgrid/labelgrid-mcp [Health: Active]

**Category:** 🎨 Art & Culture  
**Repository:** https://github.com/labelgrid/labelgrid-mcp  
**GitHub Stars:** 3  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/labelgrid-labelgrid-mcp

## Description
Official LabelGrid server — manage your music distribution catalog, releases, analytics and royalties from any MCP client.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "labelgrid-mcp": {
    "command": "npx",
    "args": ["-y","labelgrid-labelgrid-mcp"],
    "env": {
      "LABELGRID_API_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `LABELGRID_API_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What labelgrid/labelgrid-mcp MCP server does

labelgrid/labelgrid-mcp MCP server connects MCP clients to the LabelGrid public API. Its 30 consolidated tools provide an agent-facing interface for managing a music distribution catalog and its related release data. The repository also includes a separate command-line package, but the MCP package is the component intended for Claude Desktop, Cursor, and other MCP clients.

Supported areas include catalog entities, releases, files, analytics, royalties, webhooks, and distribution. The available material does not provide the individual MCP tool names or argument schemas, so implementation details should be checked in the package-specific documentation before building an automated workflow.

## How it works

The project is organized as an npm workspace. `@labelgrid/mcp` supplies the MCP server, while `@labelgrid/core` provides the shared HTTP API client used by LabelGrid tools. The core client handles structured API errors, presigned-URL uploads, content-type allowlists, catalog-entity registration, and redacted logging according to the repository description.

An MCP client starts the server and invokes its consolidated tools. Requests are sent to the LabelGrid public API through the shared client. The repository also documents a built server entry point at `node packages/mcp/dist/index.js`, which applies when the workspace has been built locally.

## Setup and configuration

The repository identifies `@labelgrid/mcp` as the published npm package for the MCP server and states that it also ships as a `labelgrid.mcpb` one-click bundle for Claude Desktop. The root development workflow uses Node 20 or newer, installs dependencies with `npm ci`, and builds the workspace with `npm run build`. That build produces the server entry point under `packages/mcp/dist`.

Access is configured with a LabelGrid API token. The repository’s quickstart shows `LABELGRID_API_TOKEN` for authenticated LabelGrid tooling. Use the MCP package documentation for the client-specific configuration format, because the supplied root README does not include the complete MCP setup block or the full tool reference.

## Tools and capabilities

labelgrid/labelgrid-mcp MCP server is intended for workflows such as:

- Searching and managing catalog records
- Creating or updating releases
- Working with release files and uploads
- Reviewing analytics and royalty information
- Managing webhooks
- Initiating or tracking distribution activities

The repository also includes an agent skill covering a full release lifecycle: drafting a release and tracks, uploading audio and artwork, validating, reviewing, distributing, and tracking delivery. That skill supplies the exact MCP tool and CLI command for each step, but those individual commands are not included in the supplied material.

## Limitations and notes

labelgrid/labelgrid-mcp MCP server depends on access to the LabelGrid public API and an appropriate API token. The provided README excerpt does not describe API quotas, LabelGrid account requirements, token scopes, error recovery behavior, or the exact safety gates used by the MCP package. It also does not establish whether LabelGrid API access itself is free or paid.

Do not confuse the MCP package with `@labelgrid/cli`, which exposes a similar API surface for terminal and script use. The root repository is a private workspace manifest; the separately published MCP package is the relevant distribution for MCP clients.

_Full upstream README: https://allmcps.com/mcp/labelgrid-labelgrid-mcp/readme_