Labelgrid Mcp

io.github.labelgridPublished by GitHub account labelgridv0.4.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyData & Analytics Business & Commerce Media & Design

Server details

Identifier: io.github.labelgrid/labelgrid-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account labelgrid for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.labelgrid%2Flabelgrid-mcp.svg)](https://sourceweft.com/mcp/io.github.labelgrid%2Flabelgrid-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Official LabelGrid MCP server that lets an assistant manage a music catalog, releases, analytics and distribution through the LabelGrid API.

What you can do: Search and manage catalog entities such as releases, labels and artists, including creating and updating drafts and uploading files through presigned URLs. Validate, review and distribute releases, and track delivery, with takedowns and immutable uploads behind a separate full-write gate. Read analytics and insights, plus finance and royalty data. Manage account details, reference data and webhooks. Expose only chosen toolsets (account, reference, catalog, releases, insights, finance, webhooks, distribution) via configuration.
When to use it: Use it when you work with LabelGrid and want an assistant to draft and prepare releases, look up catalog items, check analytics or royalties, or walk through the release-to-distribution flow without leaving the chat.
Requirements: Runs locally over stdio as the npm package @labelgrid/mcp, so Node.js is needed. A LabelGrid account and an API token in LABELGRID_API_TOKEN, created in the dashboard under Profile then API Tokens; without it the server starts in setup mode. Network access to the LabelGrid API, whose base URL can be overridden with LABELGRID_API_URL.

Before you install

Requires a LabelGrid API token, a credential that grants access to your catalog. Safe writes (creating and updating drafts, labels, artists) are enabled by default; set LABELGRID_ENABLE_WRITES to false or LABELGRID_READ_ONLY to true for read-only use. Full writes such as distribution, takedowns and immutable uploads need both LABELGRID_ENABLE_FULL_WRITES and an exact acknowledgment in LABELGRID_FULL_WRITES_ACK, and can affect live releases.

Installation

In SourceWeft

Open Labelgrid Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Package	What it is
`@labelgrid/mcp`	The 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/cli`	The `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/core`	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.

Command-line tool

Full docs (auth setup, every command group, scripting, safety model) live in packages/cli/README.md. Quickstart:

bash

npm install -g @labelgrid/cli          # Node 20+; installs the `labelgrid` commandexport LABELGRID_API_TOKEN=...         # or run `labelgrid auth login`labelgrid auth whoami                  # verify the tokenlabelgrid catalog search --type release --json | jq '.data[].id'

npm install -g @labelgrid/cli          # Node 20+; installs the `labelgrid` commandexport LABELGRID_API_TOKEN=...         # or run `labelgrid auth login`labelgrid auth whoami                  # verify the tokenlabelgrid 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

bash

npm ci            # install the whole workspacenpm run build     # build core, then mcp and clinpm test          # unit suites for every packagenpm run lint      # biome over the repo

npm ci            # install the whole workspacenpm run build     # build core, then mcp and clinpm test          # unit suites for every packagenpm 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

Source: README.md at commit 436121d

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.4.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts