@audiolabtools/mcp-server
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.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@audiolabtools/mcp-serverAnalyze the loudness of https://example.com/track.wav"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@audiolabtools/mcp-server
MCP (Model Context Protocol) server that gives any MCP-capable AI — Claude Desktop, Claude Code, Cursor, and others — nine 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 analyse a public URL or a local file on your machine.
Install
Point your MCP client at the package via npx (nothing to install globally):
{
"mcpServers": {
"audiolab": {
"command": "npx",
"args": ["-y", "@audiolabtools/mcp-server"],
"env": { "AUDIOLAB_API_KEY": "al_live_yourkey" }
}
}
}Get a key: sign in at https://audiolab.tools/account and generate one (free tier available).
Related MCP server: MusicGPT MCP Server
Requirements
Node ≥ 18 — uses the built-in global
fetch+AbortSignal.timeout.An
AUDIOLAB_API_KEY. 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 50 MB) upload over a one-shot signed URL, are analysed, and are then deleted. (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 + dominant band |
| Voice QA: speech/silence ratio, speaking rate, SNR, noise floor, room echo, sibilance & clipping risk |
| Voiced regions with start/end + per-segment RMS (auto-trim, chapters) |
| Content-type guess, tags, clipping/silence regions, brightness & dynamics buckets |
| 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“Run loudness on ./master.wav” →
analyze_loudnesswithpath“Does ./mix.mp3 pass Spotify?” →
check_targetwithpath+target:"spotify"
Configuration (env)
Var | Default | Purpose |
| — (required) | Your API key. |
|
| Override the API base (must be |
|
| Per-request timeout in milliseconds. |
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 sent to the API (small files inline; larger
files via a private one-shot signed upload that is deleted right after analysis). The API
returns numbers only and does not retain your audio (see https://audiolab.tools/privacy).
This package has no telemetry and writes nothing to disk. If audio must never leave the
machine, don't use a hosted analyser.
Limits
Local files: up to 50 MB (host bigger ones at a public URL).
One file per call (agents loop for many); one-shot (no streaming/realtime).
Rate and monthly limits are enforced by the API, per key.
Smoke test
node hosted-server.mjs --selftest # verifies the 9 tools + guards; no networkLicense
MIT © Nathan Renting
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Audio-Launch/audiolab-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server