@audiolabtools/mcp-server
This MCP server gives MCP-capable AI clients ten hosted audio-analysis tools for public URLs or local files, with no local audio engine required.
Measure loudness and dynamics: integrated LUFS, true peak, LRA, crest factor, stereo correlation, mono compatibility, tonal balance.
Check audio against delivery targets such as Spotify, Apple Music, YouTube, podcast, EBU/ATSC broadcast, or custom LUFS/true-peak targets.
Get loudness-over-time data and waveform peaks for charts, meters, and waveform UIs.
Retrieve FFT spectrum data and 7-band energy breakdowns.
Run voice QA: speech/silence ratio, speaking rate, SNR, noise floor, pause energy, sibilance, clipping risk.
Extract voiced speech segments with start/end timestamps and per-segment RMS.
Index a signal: content-type guess, tags, clipping/silence regions, brightness/dynamics buckets, dominant band.
Analyze against named profiles such as voice, master, provenance, dataset, environment, broadcast, loop, or basic.
Compare two tracks A/B for loudness.
Batch one analysis route over up to 20 URLs and/or local paths.
Use local files up to 150 MB (4 MB inline; larger via signed upload) or public HTTPS URLs; analysis runs on the hosted AudioLab API.
Allows checking audio loudness and delivery specifications for Amazon Music, ensuring compliance with platform requirements.
Allows checking audio loudness and delivery specifications for Apple Music, ensuring compliance with platform requirements.
Allows checking audio loudness and delivery specifications for Spotify, ensuring compliance with platform requirements.
Allows checking audio loudness and delivery specifications for Tidal, ensuring compliance with platform requirements.
Allows checking audio loudness and delivery specifications for YouTube, ensuring compliance with platform requirements.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@audiolabtools/mcp-server
MCP (Model Context Protocol) server that gives any MCP-capable AI (Claude Desktop, Claude Code, Cursor, and others) ten audio-analysis tools, backed by the hosted AudioLab API. It is a thin HTTP client: no local audio engine, no ffmpeg, nothing to compile. It can measure a public URL or a local file on your machine, but the measuring always happens on the hosted API: the file is read here and uploaded there (see Privacy).
Install
Point your MCP client at the package via npx (nothing to install globally). No account
needed for a first score:
{
"mcpServers": {
"audiolab": {
"command": "npx",
"args": ["-y", "@audiolabtools/mcp-server"]
}
}
}Without a key you are on the keyless trial: 20 calls a month and 3 a minute per IP address, for single analyses of a URL or a local file up to 4 MB. Batches and larger files need a key. A free key gives 1,000 calls and 2 GB a month, no card: sign in at https://audiolab.tools/account, generate one, and add it:
"env": { "AUDIOLAB_API_KEY": "al_live_yourkey" }Related MCP server: Audio Analysis MCP Server
Requirements
Node ≥ 18: uses the built-in global
fetch+AbortSignal.timeout.Optionally an
AUDIOLAB_API_KEY(see Install). No ffmpeg, no native dependencies.
Tools
Every tool takes one audio source: a public url or a local path:
{ url: "https://…" }: a public https URL the API fetches server-side.{ path: "./mix.wav" }: a file on the machine running this server. Files up to 4 MB are sent inline; larger files (up to 150 MB) upload over a signed URL, are analysed, and are swept from storage within the hour. (Localpathworks only in this stdio server, not the remote/mcpendpoint.)
Tool | Returns |
| Integrated LUFS (EBU R128 / BS.1770-4), true-peak (dBTP), LRA, crest factor, stereo correlation, mono compatibility, tonal balance |
| Pass/fail vs a delivery target ( |
| Short-term LUFS over time + downsampled waveform peaks ( |
| FFT magnitude data + 7-band energies |
| Voice QA: speech/silence ratio, speaking rate, SNR, noise floor, pause energy, sibilance & clipping risk |
| Voiced regions with start/end + per-segment RMS (auto-trim, chapters) |
| Content-type guess, tags, clipping/silence regions, brightness & dynamics buckets. Add |
| One named question, |
| A/B on two sources ( |
| One route over up to 20 sources in a single call ( |
Example asks to your AI:
“Analyze the loudness of https://example.com/track.wav” →
analyze_loudnesswithurl“Is this take usable?” →
analyze_profilewithprofile:"voice"“Has this file been re-encoded, and is it all one source?” →
analyze_profilewithprofile:"provenance"“Which of these recordings were upsampled?” →
analyze_batchwithendpoint:"signallab/index"andbandLimit:true“Run loudness on ./master.wav” →
analyze_loudnesswithpath“Does ./mix.mp3 pass Spotify?” →
check_targetwithpath+target:"spotify"
Configuration (env)
Var | Default | Purpose |
| – (optional) | Your API key. Without it: the keyless trial (20 calls a month per IP, no batches, files up to 4 MB). |
|
| Override the API base (must be |
|
| Per-request timeout in milliseconds (long files and batches stream server-side and can legitimately take minutes). |
Privacy
Analysis happens on the AudioLab API, so the audio does reach audiolab.tools: a url
is fetched server-side, and a local path is read here and uploaded to the API (small
files in the request body; larger files via a private one-shot signed upload into EU
storage). The API returns numbers only and does not keep your audio: a direct request
is decoded and discarded inside the request, and a signed upload is swept from storage
within the hour (see https://audiolab.tools/privacy). This package has no telemetry and
writes nothing to disk. There is no offline mode, and the engine is not published as an
installable package. If audio must never leave the machine, don't use a hosted analyser;
the in-browser labs on the website measure on-device, but they are for people, not for
agents.
Limits
Local files: up to 150 MB (host bigger ones at a public URL).
Duration: loudness routes (
analyze_loudness,check_target,analyze_timeseries,get_spectrum) handle long files (podcast episodes, full sets, up to ~3 h) via server-side streaming; voice/signal routes are limited to ~7 minutes.One file per call (agents loop for many); one-shot (no streaming/realtime).
Rate and monthly limits are enforced by the API, per key (per IP address on the keyless trial).
Smoke test
node hosted-server.mjs --selftest # verifies the 10 tools + guards; no networkLicense
MIT © Nathan Renting
Available Tools
10 toolsanalyze_batchBatch: one analysis route over many filesA
Run one analysis route over up to 20 audio sources in a single call. Returns per-item ok/data/error; each item is metered as one call. Routes: mixlab/analyze (default), mixlab/check-target, mixlab/timeseries, mixlab/spectrum, voicelab/qa, voicelab/segments, signallab/index. Use for folder QA, library indexing, or checking a whole release against a loudness target. Sources: public https urls and/or local file paths.
Inputs: tp, lufs, urls, paths, +2 more.
analyze_loudnessAnalyze loudness (MixLab)B
Loudness and dynamics for a track: integrated LUFS (EBU R128 / BS.1770-4), true-peak (dBTP), loudness range (LRA), crest factor, stereo correlation, mono compatibility, and tonal balance. Audio source: a public https URL, or a local file path (path).
Inputs: url, path.
analyze_profileAnalyse against a profileA
Measure a file against a named working set of lenses and get back only what that question needs. Profiles: voice (is this take usable, and which phrase is the problem), master (will this translate to real platforms and speakers), provenance (what has been done to this file, and is it all one source), dataset (which of these files are good enough, and why not the rest), environment (what is in this space, and what kind of noise is it), broadcast (does this file meet the delivery spec), loop (is this loop clean, on the grid, and safe to drop in a DAW). basic is the free tier; the other seven need a paid plan. Results are keyed by stable lens id. Only the analysis passes the profile needs are run. Set series:true to also get the curves, the per-block lanes and the per-phrase values,a much larger payload, so leave it off unless you are going to read them. Audio source: a public https URL, or a local file path (path).
Inputs: profile (required), url, path, series.
analyze_timeseriesLoudness over time (for graphing / visualization)B
Short-term LUFS samples over time (EBU R128, ~3s window) with their time-base, plus downsampled waveform peaks. Arrays suitable for loudness-over-time charts, level meters, and waveform UIs. Audio source: a public https URL, or a local file path (path).
Inputs: url, path, waveformPoints.
analyze_voiceAnalyze voice quality (VoiceLab)A
Speech-quality QA for a voice recording: speech/silence ratio, speaking-rate label, signal-to-noise, noise floor, pause energy, sibilance risk, clipping severity. Gates a voice take. Audio source: a public https URL, or a local file path (path).
Inputs: url, path.
check_targetCheck audio against a loudness target (Spotify, EBU, etc.)A
Verify whether audio hits a delivery target (Spotify -14 LUFS / EBU broadcast -23 / podcast -16 / etc.). Returns pass/fail with per-metric deltas and a concrete ffmpeg loudnorm command to fix if failing. Presets: spotify, apple-music, youtube, tidal, amazon-music, podcast, ebu-broadcast, atsc-broadcast; or target="custom" with lufs+tp. Audio source: a public https URL, or a local file path (path).
Inputs: target (required), tp, url, lufs, +1 more.
compare_loudnessCompare two tracks (A/B)A
Run loudness analysis on TWO sources and return both results for an A/B comparison: master vs reference, before vs after a fix, two encoders, two cuts. Audio source: a public https URL, or a local file path (path).
Inputs: urlA, urlB, pathA, pathB.
get_spectrumFFT spectrum dataA
Frequency-domain magnitude data (paired frequency/magnitude arrays) plus energies in 7 standard bands (sub/bass/lowMid/mid/highMid/presence/air). There is no dominant-band field in the response. For spectrum-analyzer UIs and tonal-balance analysis. Audio source: a public https URL, or a local file path (path).
Inputs: url, path.
get_speech_segmentsSpeech segments (VoiceLab)A
List voiced speech regions with start/end timestamps and per-segment RMS. For auto-trim, chapter generation, and speaker-turn detection. RMS-based voice-activity detection, not speaker diarization. Audio source: a public https URL, or a local file path (path).
Inputs: url, path.
index_signalIndex a signal (SignalLab)A
A metadata index for any audio file: content-type guess (voice/music/mixed/noise/silence) with confidence, brightness & dynamics buckets, dominant band, clipping/silence regions, and tag suggestions. For triage or auto-tagging a library. Audio source: a public https URL, or a local file path (path).
Inputs: url, path.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
TDQS
Scored across 10 tools
Most tools target a distinct analysis lens (loudness, spectrum, voice, segments, index), but analyze_profile is an umbrella that overlaps with analyze_voice, analyze_loudness, and index_signal, and analyze_timeseries sits close to analyze_loudness. Descriptions largely disambiguate by scoping each to a specific output, so confusion is limited to a couple of pairs.
All ten tools follow a consistent snake_case verb_noun pattern (analyze_loudness, check_target, get_spectrum, compare_loudness, index_signal, analyze_batch). No mixed conventions or stylistic outliers.
Ten tools is well within the sweet spot and each earns its place: distinct analysis lenses, a target checker, a comparator, and a batch runner. Nothing feels redundant or thin.
The surface covers the core audio-QA lifecycle: measurement (loudness, spectrum, timeseries), voice QA, indexing, target verification, comparison, and batch runs. Minor gaps like no dedicated silence/clipping-region extractor or format/provenance-specific operation are largely absorbed by analyze_profile and index_signal.
Maintenance
Related MCP Connectors
AI-manageable audio CDN: upload, transcode, normalize, stream & deliver audio, plus grounded docs.
AI transcription API: turn voice memos, meetings and audio URLs into text and SRT subtitles.
Audio and video tools for your AI assistant: remove noise, enhance voices, transcribe, and more.
AI mixing and mastering: analyze your mixes, run DSP autofix, render stems, and master tracks.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables audio file analysis using Google's Gemini multimodal models with support for additional context and system instructions to guide the model's behavior.1-
- FlicenseAqualityDmaintenanceEnables AI models to analyze audio files through numerical fingerprints, pitch tracking, and visual spectrograms without requiring direct audio playback. It provides tools for comparing audio iterations and detecting patterns using token-efficient analysis operations.14-
- FlicenseNot gradedqualityDmaintenanceAnalyzes audio files to extract exact, reproducible measurements like loudness, tempo, key, spectral balance, and clipping for LLM-based DAW control.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to analyze audio files, extracting tempo, key, beat drops, volume surges, high tones, loudness, brightness, and structure, and returning structured JSON and visualizations.2MIT