Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Labelgrid MCP

by labelgridversion 0.4.0i★ –iRuns on your computer
Registry nameio.github.labelgrid/labelgrid-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Marketing & social media
  • You need to fill in: LABELGRID_API_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: LABELGRID_API_TOKEN, LABELGRID_API_URL, LABELGRID_ENABLE_WRITES, LABELGRID_ENABLE_FULL_WRITES, LABELGRID_FULL_WRITES_ACK, LABELGRID_TOOLSETS, LABELGRID_READ_ONLY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "labelgrid": {
      "command": "npx",
      "args": [
        "-y",
        "@labelgrid/mcp"
      ],
      "env": {
        "LABELGRID_API_TOKEN": "your-value",
        "LABELGRID_API_URL": "your-value",
        "LABELGRID_ENABLE_WRITES": "your-value",
        "LABELGRID_ENABLE_FULL_WRITES": "your-value",
        "LABELGRID_FULL_WRITES_ACK": "your-value",
        "LABELGRID_TOOLSETS": "your-value",
        "LABELGRID_READ_ONLY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add labelgrid --env LABELGRID_API_TOKEN=your-value --env LABELGRID_API_URL=your-value --env LABELGRID_ENABLE_WRITES=your-value --env LABELGRID_ENABLE_FULL_WRITES=your-value --env LABELGRID_FULL_WRITES_ACK=your-value --env LABELGRID_TOOLSETS=your-value --env LABELGRID_READ_ONLY=your-value -- npx -y @labelgrid/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "labelgrid": {
      "command": "npx",
      "args": [
        "-y",
        "@labelgrid/mcp"
      ],
      "env": {
        "LABELGRID_API_TOKEN": "your-value",
        "LABELGRID_API_URL": "your-value",
        "LABELGRID_ENABLE_WRITES": "your-value",
        "LABELGRID_ENABLE_FULL_WRITES": "your-value",
        "LABELGRID_FULL_WRITES_ACK": "your-value",
        "LABELGRID_TOOLSETS": "your-value",
        "LABELGRID_READ_ONLY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "labelgrid": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@labelgrid/mcp"
      ],
      "env": {
        "LABELGRID_API_TOKEN": "your-value",
        "LABELGRID_API_URL": "your-value",
        "LABELGRID_ENABLE_WRITES": "your-value",
        "LABELGRID_ENABLE_FULL_WRITES": "your-value",
        "LABELGRID_FULL_WRITES_ACK": "your-value",
        "LABELGRID_TOOLSETS": "your-value",
        "LABELGRID_READ_ONLY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account labelgrid, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Marketing & social mediai

  • More stars than 0% of the other 2958 servers in this category
  • Published to the registry more recently than 21% of the other 2958 servers in this category
  • Basic checks equal to or better than 100% of the other 2958 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Labelgrid MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LABELGRID_API_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 9 days ago
Install

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 9 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Ask PopNx