Mastering as a tool for your AI agent
Magic Master speaks the Model Context Protocol. Connect the server once and your agent — in Claude, ChatGPT, Cursor or your own on an SDK — measures the track, strips the Suno/Udio AI fingerprint and masters it for the destination.
Connect
Remote server, nothing to install. One address:
https://magicmaster.pro/mcpOne click:
Add to Cursor Install in VS Code Recipes on GitHub
In claude.ai / Claude Desktop: Settings → Connectors → “Add custom connector” → URL https://magicmaster.pro/mcp/oauth (OAuth sign-in — this is how the paid tools work too). In ChatGPT: Developer mode → Connectors → create with the same URL.
In Claude Code it is one line:
claude mcp add --transport http magicmaster https://magicmaster.pro/mcp/oauthClient speaks stdio only? Bridge with npx -y mcp-remote https://magicmaster.pro/mcp/oauth (or the package npx -y magicmaster-mcp).
Send the account key in the X-API-Key header. Authorization: Bearer is accepted here ONLY for OAuth tokens (issued for /mcp) — an account JWT in that header returns 401 and breaks even the free calls. Without any key the free tools still work.
Example prompts
Once connected, just ask in plain words — the agent picks the tools itself.
- “Check this track — is it already brickwalled? https://example.com/track.wav” analyze_track
- “Remove the Suno fingerprint from this track and master it for Spotify” clean_ai_trace → master_track → get_job
- “What does a master cost and how many free runs do I have left?” get_pricing, check_limits
- “Master this for a podcast at −16 LUFS and show me the passport” master_track → get_job (widget)
Tools
| Tool | What it does | Cost |
|---|---|---|
analyze_track | LUFS, sample peak, duration, correlation, genre hint | free |
clean_ai_trace | Strips the Suno/Udio digital fingerprint, loudness untouched | free |
preview_styles | The middle 24 s in several presets at once: loudness of each and a listen link (6 per day) | free |
master_track | Mastering: 24 presets, LUFS target, export in 6 formats | 1 token |
batch_master | A whole album: shared settings, relative loudness between tracks kept | one token per track |
get_job | Status and result metrics — with the mastering passport right in the chat | free |
check_limits | Balance, free quota left and when it resets | free |
list_presets, get_pricing | Presets with their target loudness and live pricing | free |
create_topup_link | Prepares a checkout for the human — the agent cannot complete a payment | free |
Where an agent starts
3 trial masters
Register your agent once — you get an API key and three full PRO masters. No card. The JWT for that call is your account token: sign up on the site and copy it from your profile. The connector (OAuth) does not grant the trial — only this call does.
Rules in one file
agents.md says what is free, what costs a token, how to pick a preset and what to do with each error.
Machine-readable manifest
agent.json is built from live prices, limits and presets — its numbers never go stale.
curl -X POST https://magicmaster.pro/api/agents/register \
-H "Authorization: Bearer <JWT>" -H "Content-Type: application/json" \
-d '{"name":"my-agent","purpose":"mastering for my users"}'If your client cannot send custom headers
Claude Desktop does not send arbitrary headers, so there is a second endpoint with OAuth 2.1: the client sees the challenge, finds the metadata and signs you in on its own. Same tools, same limits, same billing.
https://magicmaster.pro/mcp/oauthClient registration at /oauth/register, metadata at /.well-known/oauth-authorization-server, PKCE required (S256), one scope: mastering. Tokens are issued for the /mcp resource only and are rejected anywhere else.
Protocol
Revision 2026-07-28 (stateless), plus compatibility with 2025-11-25 and 2025-06-18. Supports server/discover, cacheable lists, prompts, resources and the MCP Apps extension — the mastering passport renders as a widget inside the conversation.
Machine-readable: /agent.json, /openapi-public.json; agent rules: /agents.md.