Audiolab MCP server

<!-- Built by scripts/build-public-mcp-repo.mjs in the AudioLab monorepo. Edit mcp/README.md there, not this copy. -->

@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 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).

Requirements

• Node ≥ 18: uses the built-in global fetch + AbortSignal.timeout.
• An AUDIOLABAPIKEY. No ffmpeg, no native dependencies.

Tools

Every tool takes one audio source: a public url or a local path:

are sent inline; larger files (up to 50 MB) upload over a one-shot signed URL, are analysed, and are then deleted. (Local path works only in this stdio server, not the remote /mcp endpoint.)

• { 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

Example asks to your AI:

• “Analyze the loudness of https://example.com/track.wav” → analyze_loudness with url
• “Is this take usable?” → analyze_profile with profile:"voice"
• “Has this file been re-encoded, and is it all one source?” → analyze_profile with profile:"provenance"
• “Run loudness on ./master.wav” → analyze_loudness with path
• “Does ./mix.mp3 pass Spotify?” → check_target with path + target:"spotify"

Configuration (env)

Shortened. The full README is on GitHub.