Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
Labelgrid is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
8
downloads a day
local
runs on your machine
840
downloads in 30d
What it does
Official LabelGrid MCP server — manage your music catalog, releases, analytics and distribution.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user labelgrid-mcp '--' npx -y @labelgrid/mcp
# 2 — ask your agent for something these tools do
# get_rate_limit, revoke_api_token, search_catalog and 15 more
Labelgrid costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LAAll 1 server
labelgrid1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Labelgrid as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user labelgrid-mcp '--' npx -y @labelgrid/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take LABELGRID_API_TOKEN (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 (Override the API base URL. Defaults to the production API.), LABELGRID_ENABLE_WRITES (Enable safe writes (create/update drafts, labels, artists, and similar). Enabled by default; set to false for read-only.), LABELGRID_ENABLE_FULL_WRITES (Enable full writes (distribution, takedowns, immutable uploads). Disabled by default; also requires LABELGRID_FULL_WRITES_ACK.), LABELGRID_FULL_WRITES_ACK (Must equal the exact acknowledgment sentence (see the README safety section) to arm full writes.), LABELGRID_TOOLSETS (Comma-separated subset of toolsets to expose (account, reference, catalog, releases, insights, finance, webhooks, distribution; pre-0.3.0 names are accepted as), LABELGRID_READ_ONLY (Force reads only; overrides both write flags. Defaults to false.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The account’s API rate budget per category (read, write, export, analytics): ceiling, remaining, and window reset.
No parameter schema on file.
Revoke a LabelGrid API token. Pass token_id to revoke a specific token; omit it to revoke the token currently in use. WARNING: revoking the current token immediately ends this session — the server loses access and stops working until you configure a new token.
No parameter schema on file.
List catalog entities of one kind, paginated. filters takes the endpoint’s own filter names, passed through verbatim — … Use get_catalog_item for full detail.
No parameter schema on file.
Retrieve one catalog entity by id, with full detail (e.g. a release’s metadata and track listing, a track’s contributors and royalty splits, a writer’s PRO/IPI).
No parameter schema on file.
Create a catalog entity: pass its attributes in fields — the API owns all validation. Required and common fields per entity: … A release is created in DRAFT state — add tracks, then run the release checks before distributing.
No parameter schema on file.
Update a catalog entity: supply only the fields to change in fields (same field sets as create_catalog_item).
No parameter schema on file.
Upload a label image (logo, dark-mode logo, or background) or an artist photo from a local image file, per target.
No parameter schema on file.
Submit a release to the stores/outlets — the FINAL action that sends it out; run_release_checks (check validate) should pass first. The server enforces the account’s weekly submission limit. Reuse the SAME idempotency_key when retrying an unobserved call; without one each call is a new submission.
No parameter schema on file.
Take a release down from ALL outlets/stores — a final action that removes it everywhere it was delivered. Re-distribution is a fresh submission.
No parameter schema on file.
Confirm a release Preflight QC placed on hold, moving it into distribution review, after reviewing the quality report and accepting the release as-is. If blocking issues remain, the blocking_issues_open error includes blocking_issues to resolve or answer with a review-issue note before retrying.…
No parameter schema on file.
Request Beatport onboarding for a label. Declined or canceled requests can be submitted again; pending requests and verified labels do not start another request. Confirm the label is correct first.
No parameter schema on file.
Static availability matrix (per section, per platform) plus platform_cadence (daily|weekly per platform). Account- and date-independent: fetch once, reuse.
No parameter schema on file.
Read a release's canonical delivery status: its overall state, current and historical delivery predicates, and one current state per outlet. The API owns all queue-history interpretation. A release outside your account is indistinguishable from an unknown release (RELEASE_NOT_ACCESSIBLE).
No parameter schema on file.
Retrieve a release's smart-link landing-page configuration: enabled state, style/mode, custom copy, action list, pre-order links. Change it via manage_release_links (action update_landing_config).
No parameter schema on file.
Add a note to a release review issue — to explain a fix or add reviewer context. review_issue_id comes from get_release_review view issues.
No parameter schema on file.
This LabelGrid MCP server is not connected to an account yet because no API token is configured. Call this tool to get step-by-step instructions to walk the user through creating a LabelGrid API token and adding it to their MCP client configuration. Returns the setup steps, ready-to-copy client…
No parameter schema on file.
Read your webhook subscriptions. view: 'config' (the default) lists them — URL, subscribed events, active state — or retrieves one when webhook_id is given.
No parameter schema on file.
Delete a track asset (track_*) or an animated cover / motion artwork video (release_motion_*). Allowed only while the parent release is an editable draft; refused once locked or distributed. Cover art cannot be deleted.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Labelgrid or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.8.1 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digestc8ba4864341ad5bb492b6e2588e0e2b3bfd8d25a29c5bc292a29b98b850a8103
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc8ba4864341ad5bb
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.8.1. Pin a release below and the command asks for exactly that one.
0.8.1
3 Oct 2026
latestNo release note was published with this version.
0.8.0
1 Oct 2026
No release note was published with this version.
0.7.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Labelgrid can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.