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, ou any Modèle Context Protocol client at one endpoint, bring ton own key, et let it create releases, manage rights, deliver DDEX to 220+ magasins, et read analytique on ton behalf.
https://mcp.tonegrid.pro/mcp
165+
Tools, one per API operation
220+
DSPs reachable
2
Environments: actif & sandbox
0
Credentials stored server-side
Ton catalogue, wired for agents
Modèle 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 fonctionner a ToneGrid account the same way a developer would with the API REST, only in natural langue.
The tool list is généré straight from the ToneGrid OpenAPI specification. When the API gains an endpoint, le agent gains a tool. Nothing to update, nothing to drift.
It is the same infrastructure ton integration already uses. The MCP server is simply a second front door, built for the tools ton 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_ et get_. Writes are create_, update_, et set_. Workflow steps are named for the verb.
Sorties & tracks
Create, update, reorder, et submit releases. Add tracks, upload masters, set version types et audio specs.
Rights & royalties
Set streaming, télécharger, UGC et sync rights, P et C lines, splits, writers, publishers, et statements.
DDEX delivery
Aperçu et XSD-validate ERN 4.3, deliver or redeliver to every attached DSP, ou issue a purge takedown.
Supply-chain control
Monetization policies, prix tiers, territory clearances, et per-DSP overrides with a resolved delivery plan.
Multi-channel ingest
Real-time JSON, async bulk, DDEX ERN XML, et CSV import, each with job tracking et validation errors.
Analytique
Flux et revenue by DSP, territory, release, et day, plus per-artist overviews across a date range.
Finance
Balances, accounting periods, sales reports, statements et CSV exports, payee statements, et payouts.
Webhooks
S'abonner to lifecycle events, rotate signing secrets, fire test events, et read per-attempt delivery logs.
Marque blanche & tenants
Onboard child tenants, resolve theme et branding, et read usage rollups for a multi-tenant network.
Connect in under a minute
Grab ton API key
Any partner plan includes a tgk_ key. It is the same key that authenticates the API REST.
Add the server to ton client
Point Claude Desktop, Claude Code, Cursor, ou any remote-MCP client at the endpoint et set ton key as a header.
Ask it to do the work
Start against sandbox, len flip to production. Destructive tools are flagged so ton 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 ton own key
Every call carries ton tgk_ key. The server forwards it et stores nothing, so there is no shared secret to leak.
Destructive tools flagged
Livraison, purge takedowns, deletes et rejects are annotated so ton agent can pause et confirm avant running them.
Sandbox first
Flip one header to run every tool against an isolated sandbox with no actif Livraison DSP, len promote to production.
Scoped & revocable
Keys are scoped to one tenant et revocable in an instant. Reads et writes are separated by tool naming.
Give ton 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, ou voir what else the API can do.