Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Loudness, true-peak and voice-quality analysis of URLs and local files via the hosted AudioLab API.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AUDIOLAB_API_KEY, AUDIOLAB_API_BASE, AUDIOLAB_TIMEOUT_MSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"audiolab": {
"command": "npx",
"args": [
"-y",
"@audiolabtools/mcp-server"
],
"env": {
"AUDIOLAB_API_KEY": "your-value",
"AUDIOLAB_API_BASE": "your-value",
"AUDIOLAB_TIMEOUT_MS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add audiolab --env AUDIOLAB_API_KEY=your-value --env AUDIOLAB_API_BASE=your-value --env AUDIOLAB_TIMEOUT_MS=your-value -- npx -y @audiolabtools/mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"audiolab": {
"command": "npx",
"args": [
"-y",
"@audiolabtools/mcp-server"
],
"env": {
"AUDIOLAB_API_KEY": "your-value",
"AUDIOLAB_API_BASE": "your-value",
"AUDIOLAB_TIMEOUT_MS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"audiolab": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@audiolabtools/mcp-server"
],
"env": {
"AUDIOLAB_API_KEY": "your-value",
"AUDIOLAB_API_BASE": "your-value",
"AUDIOLAB_TIMEOUT_MS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
AUDIOLAB_API_BASE envAUDIOLAB_TIMEOUT_MS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain audiolab.tools (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: AUDIOLAB_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Intervals MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Remote MCP server for intervals.icu run data and analysis
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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).
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" }
fetch + AbortSignal.timeout.AUDIOLAB_API_KEY (see Install). No ffmpeg, no native dependencies.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. *(Local path works only in this stdio server, not the remote /mcp endpoint.)*| Tool | Returns |
|---|---|
analyze_loudness | Integrated LUFS (EBU R128 / BS.1770-4), true-peak (dBTP), LRA, crest factor, stereo correlation, mono compatibility, tonal balance |
check_target | Pass/fail vs a delivery target (spotify / apple-music / youtube / tidal / amazon-music / podcast / ebu-broadcast / atsc-broadcast, or target:"custom" + lufs+tp), with per-metric deltas and an ffmpeg loudnorm fix command |
analyze_timeseries | Short-term LUFS over time + downsampled waveform peaks (waveformPoints?) |
get_spectrum | FFT magnitude data + 7-band energies |
analyze_voice | Voice QA: speech/silence ratio, speaking rate, SNR, noise floor, pause energy, sibilance & clipping risk |
get_speech_segments | Voiced regions with start/end + per-segment RMS (auto-trim, chapters) |
index_signal | Content-type guess, tags, clipping/silence regions, brightness & dynamics buckets |
analyze_profile | One named question, voice, master, provenance, dataset, environment, broadcast, loop, room (reverberation from a clap, a pop, an impulse response or a sweep; pass roomSource), chain (lost packets) or pitch (where a voice sits and how clean it is), answered with only the lenses it needs. These ten need a paid plan; the free tier gets the basic profile, keyed by stable lens id. Add series:true for the curves, per-block lanes and per-phrase values. Carries a note when the profile’s voice lenses land on non-speech material. Full catalogue: https://audiolab.tools/lenses |
compare_loudness | A/B on two sources (urlA/pathA + urlB/pathB), returns both results |
analyze_batch | One route over up to 20 sources in a single call (urls and/or paths), per-item ok/data/error. For folder QA, library indexing, or checking a whole release against a target. Each item meters as one call |
Example asks to your AI:
analyze_loudness with urlanalyze_profile with profile:"voice"analyze_profile with profile:"provenance"analyze_loudness with pathcheck_target with path + target:"spotify"| Var | Default | Purpose |
|---|---|---|
AUDIOLAB_API_KEY | – (optional) | Your API key. Without it: the keyless trial (20 calls a month per IP, no batches, files up to 4 MB). |
AUDIOLAB_API_BASE | https://audiolab.tools/v1 | Override the API base (must be https://). |
AUDIOLAB_TIMEOUT_MS | 330000 | Per-request timeout in milliseconds (long files and batches stream server-side and can legitimately take minutes). |
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.
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.node hosted-server.mjs --selftest # verifies the 10 tools + guards; no network
MIT © Nathan Renting