Labelgrid Mcp

io.github.labelgrid由 GitHub 账号 labelgrid 发布v0.4.0更新于 Oct 24, 2026

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

已验证STDIO仅桌面数据与分析商业与电商媒体与设计

概览

AI 生成的概览

LabelGrid 官方 MCP 服务器，让助手通过 LabelGrid API 管理音乐目录、发行作品、分析数据和分发。

可以做什么
搜索和管理目录实体，如发行作品、厂牌和艺人，包括创建和更新草稿，并通过预签名 URL 上传文件。校验、审核并分发作品，跟踪交付状态；下架和不可变上传由单独的全写入开关控制。读取分析洞察以及财务和版税数据。管理账户信息、参考数据和 webhook。可通过配置只开放选定的工具集（account、reference、catalog、releases、insights、finance、webhooks、distribution）。
适用场景
当你使用 LabelGrid，并希望助手在不离开对话的情况下起草和准备发行作品、查询目录条目、查看分析或版税数据，或走完从发行到分发的流程时使用。
运行要求
以 npm 包 @labelgrid/mcp 通过 stdio 在本地运行，需要 Node.js。需要 LabelGrid 账户，并在 LABELGRID_API_TOKEN 中提供 API 令牌，可在仪表盘的 Profile 下 API Tokens 创建；没有令牌时服务器会进入设置模式。需要访问 LabelGrid API 的网络，基础地址可用 LABELGRID_API_URL 覆盖。
安装前请注意
需要 LabelGrid API 令牌，这是可访问你目录的凭据。安全写入（创建和更新草稿、厂牌、艺人）默认开启；如需只读，将 LABELGRID_ENABLE_WRITES 设为 false 或将 LABELGRID_READ_ONLY 设为 true。分发、下架和不可变上传等全写入需同时设置 LABELGRID_ENABLE_FULL_WRITES 并在 LABELGRID_FULL_WRITES_ACK 中填写准确的确认语句，可能影响已上线的作品。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Labelgrid Mcp，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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:

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'

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

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

来源：README.md，提交 436121d

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v0.4.0最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分