Run distribution
from an AI agent.
The ToneGrid MCP server turns the entire partner API into tools an AI agent can call. Point Claude, Cursor, or any Model Context Protocol client at one endpoint, bring your own key, and let it create releases, manage rights, deliver DDEX to 220+ stores, and read analytics on your behalf.
https://mcp.tonegrid.pro/mcp
165+
Tools, one per API operation
220+
DSPs reachable
2
Environments: live & sandbox
0
Credentials stored server-side
Your catalogue, wired for agents
Model Context Protocol is the open standard that lets AI assistants call real tools. The ToneGrid MCP server implements it as a remote endpoint, so any MCP client can operate a ToneGrid account the same way a developer would with the REST API, only in natural language.
The tool list is generated straight from the ToneGrid OpenAPI specification. When the API gains an endpoint, the agent gains a tool. Nothing to update, nothing to drift.
It is the same infrastructure your integration already uses. The MCP server is simply a second front door, built for the tools your team is starting to rely on.
you › release "Midnight in Lagos" to Spotify and Apple Music agent calls: create_releases → draft created create_releases_tracks → track added create_releases_dsps → 2 stores selected submit_releases → sent to review agent › Done. Release is in review for 2 stores, live date 12 Jul.
One tool for every operation
Reads are list_ and get_. Writes are create_, update_, and set_. Workflow steps are named for the verb.
Releases & tracks
Create, update, reorder, and submit releases. Add tracks, upload masters, set version types and audio specs.
Rights & royalties
Set streaming, download, UGC and sync rights, P and C lines, splits, writers, publishers, and statements.
DDEX delivery
Preview and XSD-validate ERN 4.3, deliver or redeliver to every attached DSP, or issue a purge takedown.
Supply-chain control
Monetization policies, pricing tiers, territory clearances, and per-DSP overrides with a resolved delivery plan.
Multi-channel ingest
Real-time JSON, async bulk, DDEX ERN XML, and CSV import, each with job tracking and validation errors.
Analytics
Streams and revenue by DSP, territory, release, and day, plus per-artist overviews across a date range.
Finance
Balances, accounting periods, sales reports, statements and CSV exports, payee statements, and payouts.
Webhooks
Subscribe to lifecycle events, rotate signing secrets, fire test events, and read per-attempt delivery logs.
White-label & tenants
Onboard child tenants, resolve theme and branding, and read usage rollups for a multi-tenant network.
Connect in under a minute
Grab your API key
Any partner plan includes a tgk_ key. It is the same key that authenticates the REST API.
Add the server to your client
Point Claude Desktop, Claude Code, Cursor, or any remote-MCP client at the endpoint and set your key as a header.
Ask it to do the work
Start against sandbox, then flip to production. Destructive tools are flagged so your agent confirms first.
client config
{
"mcpServers": {
"tonegrid": {
"type": "http",
"url": "https://mcp.tonegrid.pro/mcp",
"headers": {
"Authorization": "Bearer tgk_your_key",
"X-ToneGrid-Env": "production"
}
}
}
}
verify it is up
$ curl https://mcp.tonegrid.pro/health {"status":"ok","tools":165, ...}
Built to hand an agent the keys, carefully
Bring your own key
Every call carries your tgk_ key. The server forwards it and stores nothing, so there is no shared secret to leak.
Destructive tools flagged
Delivery, purge takedowns, deletes and rejects are annotated so your agent can pause and confirm before running them.
Sandbox first
Flip one header to run every tool against an isolated sandbox with no live DSP delivery, then promote to production.
Scoped & revocable
Keys are scoped to one tenant and revocable in an instant. Reads and writes are separated by tool naming.
Give your agent the whole platform
The MCP server is one of the advanced capabilities ToneGrid ships for teams building on the platform. Read the full tool reference, or see what else the API can do.