Magic Master — Audio Mastering vs MCP for Adobe Premiere Pro

A side-by-side look at the Magic Master — Audio Mastering and MCP for Adobe Premiere Pro 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 declaredMCP for Adobe Premiere Pro logoMCP for Adobe Premiere ProMultimedia Process · Local subprocess (stdio)Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check.72GreatAuth: no auth required

Verdict: choose Magic Master — Audio Mastering for multimedia process work as a local process; choose MCP for Adobe Premiere Pro 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

MCP for Adobe Premiere Pro logoChoose MCP for Adobe Premiere Pro 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.
  • You want tools like get_project_info, list_project_items, list_sequences.
Explore MCP for Adobe Premiere Pro

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMagic Master — Audio Mastering logoMagic Master — Audio MasteringMCP for Adobe Premiere Pro logoMCP for Adobe Premiere Pro
CategoryMultimedia ProcessMultimedia Process
Quality signal56/100 · Good72/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2427
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools11432

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.

MCP for Adobe Premiere Pro tools 432

  • get_project_infoGet information about the currently open Premiere Pro project
  • list_project_itemsList all items in the project panel (clips, bins, sequences)
  • list_sequencesList all sequences in the project
  • get_active_sequenceGet bounded, paged information about the currently active sequence (50 clips by default). Follow pagination.nextOffset for more
  • list_sequence_tracksList all tracks (video and audio) in a sequence
  • get_clip_propertiesGet detailed properties of a specific clip by its node ID
  • find_project_item_by_nameFind a project item by name (searches recursively through bins)
  • get_sequence_settingsGet the settings (resolution, frame rate, etc.) of a sequence
  • get_selected_clipsGet the currently selected clips in the active sequence
  • get_clip_at_positionGet the clip at a specific time position on a track
  • save_projectSave the current Premiere Pro project to its existing path. Fails when the project has never been saved (use save_project_as) or when Premiere writes no non-empty file. Fresh disk metadata verifies a save; unchanged or unreadable metadata reports committed_unverified.
  • save_project_asSave the current project to a new .prproj path. Premiere then has the NEW copy open and closes the original, so later edits go to the copy; the result reports both paths. Fails when Premiere writes no file or leaves a pre-existing path unchanged. Use open_project to return to the original.
  • +420 more on 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"
      ]
    }
  }
}

MCP for Adobe Premiere Pro

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-for-adobe-premiere-pro": {
      "command": "npx",
      "args": [
        "-y",
        "premiere-pro-mcp"
      ]
    }
  }
}

Frequently asked questions

Magic Master — Audio Mastering is categorized under Multimedia Process and uses a local stdio subprocess. MCP for Adobe Premiere Pro belongs to Multimedia Process and uses a local stdio subprocess. Pick Magic Master — Audio Mastering for multimedia process work and MCP for Adobe Premiere Pro 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. MCP for Adobe Premiere Pro 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 mcp-for-adobe-premiere-pro 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. MCP for Adobe Premiere Pro has 72/100 (Great) with 4 views, 0 installs and 427 GitHub stars.