MCP.Market

Labelgrid MCP server

by labelgrid·io.github.labelgrid/labelgrid-mcp·v0.4.0·3 stars
No reviews yet

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

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

3 stars69 downloads/wk

Reviews

Write one

Nobody has reviewed Labelgrid yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Labelgrid tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan42 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Labelgrid compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
GitHub stars
3
more than 80% of 28,688 servers
Downloads a week
69
more than 53% of 12,191 servers with a package

Install Labelgrid in Claude Code, Cursor or VS Code

Runs npx -y @labelgrid/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add labelgrid-mcp -- npx -y @labelgrid/mcp
Add to Cursor

What the publisher says

From the Labelgrid repository's README, as published. We do not edit it. Read it on GitHub

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

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

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.

  • The root package.json is a private workspaces manifest; its scripts fan out to the

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

  • Each package has its own tsconfig.json extending the shared tsconfig.base.json

@labelgrid/core to the sibling package's TypeScript source, so running tests never requires a prior core build.

  • Unit tests run per package via each package's vitest.config.ts. The MCP package aliases

npm run leak-guard, npm run check-coverage, npm run gen-docs, npm run measure-tokens.

  • Repo-wide checks live in scripts/ and run from the root: npm run lint,

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Labelgrid: common questions

Is Labelgrid MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Labelgrid safety report
How do I install Labelgrid?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Labelgrid need an API key?
Yes. The registry entry asks for LABELGRID_API_TOKEN.
Is Labelgrid maintained?
The last commit was 43 days ago (2026-09-22). The latest release is v0.4.0.
How does Labelgrid compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers); downloads a week 69 (more than 53% of 12,191 servers with a package). Full comparison.