Add AudioLab to any AI.

Every route needs one API key. It is the rights boundary: an MCP call and a curl call with the same key get the same tools, the same 60-requests-per-minute limit, and the same fetch protection. Sign in and generate one from your account, free tier included.

One command adds the skill and the MCP server, and prompts for your key:

/plugin marketplace add Audio-Launch/audiolab-claude-plugin
/plugin install audiolab@audiolab-tools

Or configure MCP by hand in any Claude client and restart:

{
  "mcpServers": {
    "audiolab": {
      "command": "npx",
      "args": ["-y", "@audiolabtools/mcp-server"],
      "env": { "AUDIOLAB_API_KEY": "your_key_here" }
    }
  }
}

OpenAI can’t run a local package, so it uses the hosted /mcp endpoint. Three ways in:

A. OpenAI API (Responses)

# tools=[{
#   "type": "mcp",
#   "server_label": "audiolab",
#   "server_url": "https://audiolab.tools/mcp",
#   "headers": {"Authorization": "Bearer YOUR_AUDIOLAB_KEY"},
#   "require_approval": "never"
# }]

B. ChatGPT Developer Mode connector

Settings → Connectors → Advanced → Developer mode on, then add a custom connector with URL https://audiolab.tools/mcp and a Bearer credential. Needs Plus, Pro, Team, Enterprise, or Edu.

C. Custom GPT (no MCP)

In the GPT editor: Actions → Import from URL → https://audiolab.tools/openapi.yaml, then Authentication: API Key, Bearer. This exposes the REST tools directly. (A/B compare is MCP-only; run two analyze calls instead.)

The google-genai SDK spawns the local package as a subprocess, so nothing new is needed:

params = StdioServerParameters(
    command="npx", args=["-y", "@audiolabtools/mcp-server"],
    env={"AUDIOLAB_API_KEY": "your_key_here"})
# async with stdio_client(params) as (r, w):
#   async with ClientSession(r, w) as session:
#     await session.initialize()
#     config = GenerateContentConfig(tools=[session])

Gemini’s hosted MCP mode (2.5-class models) can also point at https://audiolab.tools/mcp with a Bearer header, and plain function-calling can be built from the OpenAPI spec.

All run the local package over stdio. Cursor uses ~/.cursor/mcp.json:

{
  "mcpServers": {
    "audiolab": {
      "command": "npx",
      "args": ["-y", "@audiolabtools/mcp-server"],
      "env": { "AUDIOLAB_API_KEY": "your_key_here" }
    }
  }
}

Windsurf uses the same shape. VS Code uses .vscode/mcp.json with "type": "stdio" and the same command.

Anything that speaks remote MCP points at one URL. In n8n: an MCP Client node, HTTP Streamable transport, URL https://audiolab.tools/mcp, header Authorization: Bearer your_key.

The universal rule for any MCP client: Streamable HTTP transport, Bearer key in the Authorization header. That is all the endpoint needs.

No MCP, no framework. The tools are a plain REST call:

curl https://audiolab.tools/v1/mixlab/analyze \
  -H "Authorization: Bearer $AUDIOLAB_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/track.wav"}'

Full reference and a no-key browser playground on the /api page. The @audiolabtools/ai-sdk provider wires the same tools into a Vercel AI SDK agent.

MCP and REST send the audio URL to the hosted API for decoding and analysis, so the audio crosses the network. For strictly on-device analysis with no upload, use the in-browser labs, which run entirely client-side. See privacy.