Log inSubmit server
Magic Master — Audio Mastering logo

Magic Master — Audio Mastering

Remote audio mastering over MCP with LUFS targets, True Peak limiting, AI-fingerprint removal, and mastering results.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Magic Master — Audio Mastering

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "magic-master-audio-mastering": {
      "command": "npx",
      "args": [
        "-y",
        "magicmaster-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Magic Master — Audio Mastering connects MCP clients to a hosted audio mastering service over streamable HTTP. Agents can analyze tracks, remove Suno or Udio fingerprints, apply mastering presets with LUFS and True Peak targets, and retrieve result metrics. Free analysis and cleanup tools require no account, while mastering uses quotas or tokens. Reach for it when an agent needs repeatable loudness processing and an auditable mastering result inside the chat workflow.

Use cases

  • Analyze generated tracks before release
  • Remove Suno or Udio fingerprints
  • Master audio to a LUFS target
  • Poll jobs for mastering metrics
  • Check quota before submitting work

Key features

  • LUFS and True Peak analysis
  • Suno and Udio fingerprint removal
  • 24 mastering presets
  • Six export formats
  • Mastering passport results
  • Quota and token management

Tools11

What Magic Master — Audio Mastering lets your agent do. Expand a tool for its parameters.

Self-reported~396 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 38d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · magicmaster-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads154Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Tools exposed11Callable tools this server registers over MCP.

How Magic Master — Audio Mastering works

What Magic Master — Audio Mastering does

Magic Master — Audio Mastering exposes hosted audio-processing operations through the Model Context Protocol. It can inspect a track, remove the digital fingerprint associated with Suno or Udio without changing loudness, and create a mastered output. The service reports loudness and technical measurements such as LUFS, True Peak, duration, and channel correlation, and can provide a genre hint.

The service is intended for agent-driven mastering rather than local audio processing. Its standard workflow is to analyze a track, optionally clean an AI-generated track, submit a mastering job, and check the job until the output is ready. A completed job includes result metrics and a mastering passport widget when the client supports MCP Apps.

How it works

The hosted endpoint is https://magicmaster.pro/mcp and uses streamable HTTP. Paid-tool access is available through the OAuth endpoint at https://magicmaster.pro/mcp/oauth. The repository contains connection recipes and a small bridge for clients that only support stdio; the actual processing remains on the hosted service.

Mastering jobs normally take 20–60 seconds. master_track supports 24 presets, a requested LUFS target, and six export formats. Agents can poll get_job for status and output measurements instead of needing to keep the original request open.

Magic Master — Audio Mastering can be used anonymously for free tools. Agent registration provides three trial masters; subsequent full PRO masters consume one token each. Tokens do not expire.

Setup and configuration

No local installation is required for clients that support HTTP MCP connections. Configure the MCP URL directly in Claude Desktop, Cursor, VS Code, or Claude Code. ChatGPT can connect through Developer mode using the OAuth URL.

For stdio-only clients, use mcp-remote or the magicmaster-mcp npm wrapper. A Docker image is also available for clients without Node; it runs the bridge and requires outbound HTTPS access to magicmaster.pro. The optional MAGICMASTER_MCP_URL setting selects the endpoint used by the bridge, including the OAuth endpoint for paid tools. The hosted server itself does not require local environment variables.

Tools and capabilities

  • analyze_track: reports LUFS, True Peak, duration, correlation, and a genre hint.
  • clean_ai_trace: removes the Suno or Udio fingerprint while leaving loudness unchanged.
  • master_track: starts mastering with a preset, LUFS target, and export format.
  • get_job: returns job status and result metrics, with the mastering passport widget.
  • check_limits: shows balance, free quota remaining, and quota reset time.
  • list_presets: returns available presets and their target loudness.
  • get_pricing and get_service_info: expose current pricing and service details.
  • create_topup_link: prepares a human checkout link; an agent cannot complete payment itself.

Magic Master — Audio Mastering is a fit for workflows that need an agent to inspect generated audio, normalize it to a delivery target, remove supported AI traces, and report measurable results. It is less suitable when processing must remain entirely on local infrastructure or when an agent must purchase tokens without human involvement.

Limitations and notes

The service is remote, so clients need network access to the hosted endpoint. Only the cleanup operation is described as preserving loudness; mastering changes the track according to its selected preset and target. Paid mastering is quota- or token-limited, and create_topup_link does not let the agent pay.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Magic Master — Audio Mastering

Magic Master — Audio Mastering is an MCP server that connects AI clients to a hosted audio mastering service. Its main tools analyze tracks, remove Suno or Udio fingerprints, create masters with LUFS targets, check job results, and report quotas. It communicates through streamable HTTP, with an OAuth endpoint for paid mastering tools.

You do not need to install the hosted server. Add `https://magicmaster.pro/mcp` to an HTTP-capable MCP client, or use `mcp-remote` or the `magicmaster-mcp` npm wrapper for stdio-only clients. A Docker bridge is also available for clients without Node.

Yes, Magic Master — Audio Mastering works with Cursor through its MCP configuration. Add the hosted URL `https://magicmaster.pro/mcp` to `.cursor/mcp.json`; no local server installation is required.

The `clean_ai_trace` tool removes the Suno or Udio digital fingerprint while leaving loudness untouched.

Related MCP servers

All in Multimedia Process All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMagic Master — Audio Mastering AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/magic-master-audio-mastering?style=directory)](https://allmcps.com/mcp/magic-master-audio-mastering)
HTML Embed
<a href="https://allmcps.com/mcp/magic-master-audio-mastering"><img src="https://allmcps.com/api/badge/magic-master-audio-mastering?style=directory" alt="Magic Master — Audio Mastering on AllMCPs" /></a>