Audio Analyzer vs Audio MCP
A side-by-side look at the Audio Analyzer and Audio MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Audio MCPMultimedia Process · Local subprocess (stdio)Audio perception for AI agents: measure, see, compare, edit and synthesize sound locally.53GoodAuth: no auth requiredVerdict: choose Audio Analyzer for multimedia process work; choose Audio 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?
Choose Audio Analyzer when
- You need dedicated capabilities in the Multimedia Process domain.
- You want tools like
audio_info, spectral_features, harmonic_analysis.
AChoose Audio 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.
- You have the keys it needs:
AUDIO_MCP_ALLOWED_DIRS, AUDIO_MCP_MAX_SECONDS, AUDIO_MCP_WHISPER_MODEL, AUDIO_MCP_ROOT, AUDIO_MCP_FFMPEG. - You want tools like
audio_analyze, audio_events, audio_view.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Audio MCP | |
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 45/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | AUDIO_MCP_ALLOWED_DIRSAUDIO_MCP_MAX_SECONDSAUDIO_MCP_WHISPER_MODELAUDIO_MCP_ROOTAUDIO_MCP_FFMPEG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 63 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | 14 |
| Full listing | View Audio Analyzer | View Audio MCP |
Tools & capabilities
Audio Analyzer tools 6
audio_infoBasic file info: duration, sample rate, sample countspectral_featuresBrightness, richness, loudness, texture, timbre (MFCCs), frequency band energy, spectral contrast, dynamic range, LUFS loudness, stereo fieldharmonic_analysisKey detection, pitch class distribution, tonnetzrhythm_analysisTempo (BPM), beat positions, tempo stabilityfull_analysisEverything above in one call, plus percussive character (HPSS), stereo field, and section boundaries. Recommended workflow: call without resolution first to get summary + section map, then zoom into interesting sections with `start_time`/`end_time` at high resolutioncompareA/B two tracks -- analyses both and returns a compact diff table
Audio MCP tools 14
audio_analyzePeak, true peak, RMS, LUFS loudness, clipping, DC offset, a loudness sparkline, silence and noise floor, stereo correlation/width/balance, band energy, brightness, tonal vs. noisy, strongest frequencies as note names, pitch, onsets, tempo, edge clicks, loop-seam quality, and an **`issues`** list in…audio_eventsSplits audio into distinct sounds and describes each one: timing, level, attack, tonal/noisy, brightness, pitch or glideaudio_viewPNG waveform and/or spectrogram, with an optional pitch overlay. Every column covers its full time span, so short clicks aren't skipped on long filesaudio_timelineLevel and brightness over time. Streams the file, so it works on recordings of any lengthaudio_melodySingle-line transcription: notes, timings, cents, compact textaudio_transcribeSpeech to text with local Whisper: timed words, language, speaking rate, long pauses and **uncertain words** *(optional extra)*audio_compareA/B summary, metric deltas, per-band dB changes, issues fixed or introduced, and a **null test** (identical? only a gain change? lightly changed?)audio_processAn ordered chain of edits written to a **new** file: gain, peak/LUFS normalize, true-peak limiter, compressor, noise reduction, RMS normalize, trim, fades, crop, pad, high/low-pass, peaking EQ, shelves, DC removal, polarity, mono/stereo, resample, reverse, seamless-loop crossfade, mix, appendaudio_batch_surveyAudits a folder for consistency (loudness outliers, mixed sample rates/channels/formats, uneven leading silence) and returns ready-to-run fixesaudio_batch_processApplies one edit chain to many files and writes them to an output folderaudio_synthesizeDeclarative synth: band-limited oscillators with phase control, noise colours (pink/brown loop seamlessly), sweeps, ADSR, vibrato, tremolo, filters, pan, note sequences, plus exact test signals (impulse, DC, silence)audio_infoMetadata for a file, or a listing of the audio files in a folder- +2 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.
Audio Analyzer
No confirmed install command for Audio Analyzer yet — follow the setup steps linked from its listing page rather than a guessed package name.
Audio MCP
{
"mcpServers": {
"audio-mcp": {
"command": "uvx",
"args": [
"audio-mcp"
],
"env": {
"AUDIO_MCP_ALLOWED_DIRS": "YOUR_AUDIO_MCP_ALLOWED_DIRS_HERE",
"AUDIO_MCP_MAX_SECONDS": "YOUR_AUDIO_MCP_MAX_SECONDS_HERE",
"AUDIO_MCP_WHISPER_MODEL": "YOUR_AUDIO_MCP_WHISPER_MODEL_HERE",
"AUDIO_MCP_ROOT": "YOUR_AUDIO_MCP_ROOT_HERE",
"AUDIO_MCP_FFMPEG": "YOUR_AUDIO_MCP_FFMPEG_HERE"
}
}
}
}
Frequently asked questions
Audio Analyzer is categorized under Multimedia Process and uses an install path we have not confirmed yet. Audio MCP belongs to Multimedia Process and uses a local stdio subprocess. Pick Audio Analyzer for multimedia process work and Audio 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. Audio Analyzer has no confirmed install command yet — follow its own setup instructions.
Audio Analyzer has no declared pricing — check the project's own site. Audio 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 audio-analyzer and audio-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Audio Analyzer has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 63 GitHub stars. Audio MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.