Back to Browse

Labelgrid MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-structured, professionally maintained MCP server for LabelGrid's music distribution API. The codebase demonstrates strong security practices including proper authentication via API tokens, input validation with Zod schemas, and careful credential handling. Minor findings around broad exception handling and logging do not meaningfully impact security posture. Permissions are appropriately scoped to the server's stated purpose of API client integration. Supply chain analysis found 3 known vulnerabilities in dependencies (2 critical, 0 high severity). Package verification found 1 issue (1 critical, 0 high severity).

5 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

Unverified package source

We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.

What You'll Need

Set these up before or after installing:

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.Required

Environment variable: LABELGRID_API_TOKEN

Override the API base URL. Defaults to the production API.Optional

Environment variable: LABELGRID_API_URL

Enable safe writes (create/update drafts, labels, artists, and similar). Enabled by default; set to false for read-only.Optional

Environment variable: LABELGRID_ENABLE_WRITES

Enable full writes (distribution, takedowns, immutable uploads). Disabled by default; also requires LABELGRID_FULL_WRITES_ACK.Optional

Environment variable: LABELGRID_ENABLE_FULL_WRITES

Must equal the exact acknowledgment sentence (see the README safety section) to arm full writes.Optional

Environment variable: LABELGRID_FULL_WRITES_ACK

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.Optional

Environment variable: LABELGRID_TOOLSETS

Force reads only; overrides both write flags. Defaults to false.Optional

Environment variable: LABELGRID_READ_ONLY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-labelgrid-labelgrid-mcp": {
      "env": {
        "LABELGRID_API_URL": "your-labelgrid-api-url-here",
        "LABELGRID_TOOLSETS": "your-labelgrid-toolsets-here",
        "LABELGRID_API_TOKEN": "your-labelgrid-api-token-here",
        "LABELGRID_READ_ONLY": "your-labelgrid-read-only-here",
        "LABELGRID_ENABLE_WRITES": "your-labelgrid-enable-writes-here",
        "LABELGRID_FULL_WRITES_ACK": "your-labelgrid-full-writes-ack-here",
        "LABELGRID_ENABLE_FULL_WRITES": "your-labelgrid-enable-full-writes-here"
      },
      "args": [
        "-y",
        "labelgrid-mcp-workspace"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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

Reviews

No reviews yet

Be the first to review this server!