Magic Master — Audio Mastering

Connect

Remote server, nothing to install. One address:

https://magicmaster.pro/mcp

One click:

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

Client speaks stdio only? Bridge with npx -y mcp-remote https://magicmaster.pro/mcp/oauth (or the package npx -y magicmaster-mcp).

Send the key in the X-API-Key header (or Authorization: Bearer with a JWT). Free tools work without one.

Tools

Tool	What it does	Cost
analyze_track	LUFS, true peak, duration, correlation, genre hint	free
clean_ai_trace	Strips the Suno/Udio digital fingerprint, loudness untouched	free
master_track	Mastering: 24 presets, LUFS target, export in 6 formats	1 token
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 the agent once and get an API key plus three full PRO masters. No card.

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/oauth

Client 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.