Magic Master — Audio Mastering vs Davinci Resolve MCP

A side-by-side look at the Magic Master — Audio Mastering and Davinci Resolve MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Magic Master — Audio Mastering logoMagic Master — Audio MasteringMultimedia Process · Local subprocess (stdio)Audio mastering for AI agents: LUFS/True Peak targets, Suno/Udio AI-fingerprint removal.56GoodAuth: not declaredDavinci Resolve MCP logoDavinci Resolve MCPMultimedia Process · Local subprocess (stdio)MCP server integration for DaVinci Resolve providing powerful tools for video editing, color grading, media management, and project control64GoodAuth: no auth required

Verdict: choose Magic Master — Audio Mastering for multimedia process work as a local process; choose Davinci Resolve MCP for multimedia process as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Magic Master — Audio Mastering logoChoose Magic Master — Audio Mastering when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_service_info, list_presets, get_pricing.
Explore Magic Master — Audio Mastering

Davinci Resolve MCP logoChoose Davinci Resolve MCP when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Davinci Resolve MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMagic Master — Audio Mastering logoMagic Master — Audio MasteringDavinci Resolve MCP logoDavinci Resolve MCP
CategoryMultimedia ProcessMultimedia Process
Quality signal56/100 · Good64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars23,701
Directory activity 0 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
Tools11Not listed

Tools & capabilities

Magic Master — Audio Mastering tools 11

  • get_service_infoWhat Magic Master does, what is free, what costs a token, and where the rules live. Call once at the start of a session.
  • list_presetsAll 24 mastering presets with their target loudness in LUFS. Gives the exact keys that `master_track` and `batch_master` accept.
  • get_pricingLive token packs and payment methods (RUB). Prices are read live, not quoted from memory.
  • check_limitsToken balance, free quota left and when it resets, upload cap, whether PRO modules are available.
  • analyze_trackIntegrated LUFS, sample peak, duration, sample rate and stereo correlation, without processing. True peak and loudness range come back from `get_job` after mastering.
  • clean_ai_traceStrips the Suno / Udio AI generator fingerprint; loudness and tone stay as they are. Returns a job id.
  • preview_stylesMasters the middle 24 seconds in 2–6 presets at once and returns each one's loudness and a listen link.
  • master_trackMasters one track. Costs 1 token when the account has a balance; otherwise it runs on the free quota without PRO modules. Returns a job id. Pass `dry_run=true` to see the price and effective settings first.
  • batch_masterMasters up to 10 tracks in one call with the same settings. `album_mode` (default `true`) keeps relative loudness between tracks. Returns one job id per track.
  • get_jobStatus, progress and result metrics (`after_lufs`, `true_peak_db`, `lra`, `platform_ready`) for a mastering, cleanup or preview job. Includes a signed `download_url` when a master is done.
  • create_topup_linkPrepares a token checkout for the human. The agent cannot complete the payment itself.

Davinci Resolve MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Magic Master — Audio Mastering

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "magic-master-audio-mastering": {
      "command": "npx",
      "args": [
        "-y",
        "magicmaster-mcp"
      ]
    }
  }
}

Davinci Resolve MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "samuelgursky-davinci-resolve-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "davinci-resolve-mcp"
      ]
    }
  }
}

Frequently asked questions

Magic Master — Audio Mastering is categorized under Multimedia Process and uses a local stdio subprocess. Davinci Resolve MCP belongs to Multimedia Process and uses a local stdio subprocess. Pick Magic Master — Audio Mastering for multimedia process work and Davinci Resolve MCP for multimedia process.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Magic Master — Audio Mastering has no declared pricing — check the project's own site. Davinci Resolve MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add magic-master-audio-mastering and samuelgursky-davinci-resolve-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Magic Master — Audio Mastering has a quality signal of 56/100 (Good) with 0 views, 0 installs and 2 GitHub stars. Davinci Resolve MCP has 64/100 (Good) with 11 views, 0 installs and 3,701 GitHub stars.