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 分