Audio Delivery Network

net.audiodeliveryPublished by audiodelivery.netOfficial publisherv0.3.3Updated Nov 2, 2026

AI-manageable audio CDN: upload, transcode, normalize, stream & deliver audio, plus grounded docs.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper ToolsMedia & Design

Overview

AI-generated overview

AudioDN MCP server that lets an assistant look up canonical AudioDN API docs and manage audio hosting: creators, collections, uploads, tracks and playback.

What you can do
  • Search and read bundled AudioDN documentation, guides and OpenAPI operation definitions
  • List, create and update creators and collections
  • Manage upload sessions and register tracks to obtain upload URLs
  • Read tracks and poll their readiness, and list delivery variants
  • Mint and read play sessions that return signed playback URLs
When to use it
Useful when an assistant helps set up audio or podcast hosting on AudioDN, or writes integration code against the AudioDN REST API and should ground answers in the canonical spec instead of guessing endpoints.
Requirements
Runs as a hosted Streamable HTTP endpoint or locally via npx from the npm package @audiodn/mcp (Node.js). Knowledge and doc tools need no key; live API tools need an AudioDN API key supplied as ADN_API_KEY locally or as an Authorization bearer token to the hosted endpoint. Optional variables: ADN_API_BASE_URL, ADN_MCP_ALLOW_DELETE, ADN_MCP_LIVE_DOCS, ADN_MCP_TIMEOUT_MS.
Before you install
The API key is described as server-side and full-access, so treat it as a sensitive secret. Create and update tools change data on the account; the client is expected to prompt for approval. Delete tools for creators and collections are hidden unless ADN_MCP_ALLOW_DELETE=1 is set, and are never exposed on the hosted endpoint. Uploading audio requires sending file bytes to the returned upload URL.

Installation

In SourceWeft

  1. Open Audio Delivery Network in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.audiodelivery%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "audio-delivery-network": {
      "type": "http",
      "url": "https://mcp.audiodelivery.net/mcp"
    }
  }
}

README

@audiodn/mcp

Model Context Protocol server for AudioDN.

Exposes the AudioDN REST API as MCP tools so AI agents (Cursor, Claude Desktop, Claude Code, VS Code, Codex, etc.) can configure audio hosting on a user's behalf, plus offline, read-only knowledge tools grounded in the canonical AudioDN OpenAPI spec and documentation so agents look up the correct endpoints instead of guessing.

Install in Cursor

One-click install (hosted endpoint, zero setup — knowledge/doc tools work immediately):

[Add AudioDN to Cursor]

To enable the live API tools, set ADN_API_KEY (an adn_... key from the dashboard) in your environment before launching Cursor; the hosted endpoint picks it up from the Authorization header. Prefer a local stdio server? Use this button instead:

[Add AudioDN (npx) to Cursor]

Both correspond to the mcp.json shipped with this plugin. See Cursor's MCP docs for manual setup.

Install

bash
npm install -g @audiodn/mcp# or run on demandnpx @audiodn/mcp

Configure

Set a server-side AudioDN API key (mint one in the dashboard at https://account.audiodeliverynetwork.com under Settings → API Keys).

bash
export ADN_API_KEY="adn_..."# Optional overrides:# export ADN_API_BASE_URL="https://api.audiodelivery.net"  # default# export ADN_MCP_ALLOW_DELETE=1     # enable destructive delete tools (off by default)# export ADN_MCP_LIVE_DOCS=1        # refresh bundled docs from the public site at startup# export ADN_MCP_TIMEOUT_MS=30000   # per-request timeout

Environment variables

VariableRequiredDefaultPurpose
ADN_API_KEYYes–Server-side, full-access API key used for all live-API tools.
ADN_API_BASE_URLNohttps://api.audiodelivery.netOverride the API host.
ADN_MCP_ALLOW_DELETENooffSet to 1 to expose the destructive adn_delete_* tools.
ADN_MCP_LIVE_DOCSNooffSet to 1 to refresh bundled docs from the public site (falls back to the bundle offline).
ADN_MCP_TIMEOUT_MSNo30000Per-request timeout in milliseconds.

Safety model

  • Reads and knowledge tools are annotated read-only and always available.
  • Create/update tools run with the API key but are annotated so MCP clients can prompt for approval; the client is the human-in-the-loop layer.
  • The two delete tools (adn_delete_creator, adn_delete_collection) are hidden and refuse to run unless the server is started with ADN_MCP_ALLOW_DELETE=1. Set it once to opt in.

Hosted (remote) endpoint

Besides the local npx stdio server above, AudioDN runs the same tool set as a hosted Streamable HTTP endpoint on Cloudflare Workers, so clients that support remote MCP servers can connect without installing anything.

  • URL: https://mcp.audiodelivery.net/mcp — the MCP endpoint. The root / serves a human landing page in a browser (and JSON for tooling), and /health returns machine-readable server info.
  • Auth — bring your own key: the endpoint is public and stores no secrets. Knowledge/doc tools work with no key. To enable the live API tools, send your AudioDN API key on every request as either header:
Authorization: Bearer adn_...# orX-ADN-API-Key: adn_...
  • Deletes are never exposed on the hosted endpoint, regardless of key.

Example client configuration (clients that support a remote/HTTP MCP URL):

json
{  "mcpServers": {    "audiodn": {      "url": "https://mcp.audiodelivery.net/mcp",      "headers": { "Authorization": "Bearer adn_..." }    }  }}

The hosted Worker lives in worker/ and is deployed with Wrangler (npm run deploy); it is not part of the published npm package.

Use with Cursor

Settings → Tools & Integrations → MCP (or edit ~/.cursor/mcp.json):

json
{  "mcpServers": {    "audiodn": {      "command": "npx",      "args": ["-y", "@audiodn/mcp"],      "env": { "ADN_API_KEY": "adn_..." }    }  }}

Use with Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (or the equivalent on your OS), then restart the app:

json
{  "mcpServers": {    "audiodn": {      "command": "npx",      "args": ["-y", "@audiodn/mcp"],      "env": { "ADN_API_KEY": "adn_..." }    }  }}

Use with Claude Code

bash
claude mcp add audiodn --env ADN_API_KEY=adn_... -- npx -y @audiodn/mcp

Use with VS Code (Copilot) / Codex / Windsurf

Any client that speaks MCP over stdio uses the same command. For VS Code, add to .vscode/mcp.json:

json
{  "servers": {    "audiodn": {      "command": "npx",      "args": ["-y", "@audiodn/mcp"],      "env": { "ADN_API_KEY": "adn_..." }    }  }}

For Codex CLI (~/.codex/config.toml):

toml
[mcp_servers.audiodn]command = "npx"args = ["-y", "@audiodn/mcp"]env = { ADN_API_KEY = "adn_..." }

Tools

Knowledge tools (read-only, offline, no API key needed)

ToolDescription
adn_aboutServer version, bundled OpenAPI version, docs source, API base.
adn_search_docsKeyword search over bundled docs + OpenAPI summaries.
adn_list_operationsList all REST operations (operationId, method, path).
adn_get_operationFull OpenAPI definition for one operationId.
adn_get_guideCanonical guide (authentication, upload, processing, playback, webhooks, variant-types, security, compatibility).
adn_list_variant_typesThe seven variant types and which are API-creatable.

Live API tools

ToolDescriptionAnnotation
adn_list_creators / adn_get_creatorRead creatorsread-only
adn_create_creator / adn_update_creatorCreate/update creatorwrite
adn_delete_creatorDelete creatordestructive (gated)
adn_list_collections / adn_get_collectionRead collectionsread-only
adn_create_collection / adn_update_collectionCreate/update collectionwrite
adn_delete_collectionDelete collection + its tracksdestructive (gated)
adn_list_tracks / adn_get_trackRead tracks; adn_get_track polls readinessread-only
adn_create_upload_session / adn_get_upload_sessionManage upload sessionswrite / read-only
adn_create_track_in_upload_sessionRegister a track, get track_upload.upload_urlwrite
adn_create_play_session / adn_get_play_sessionMint/read play sessions (scope: collection, track)write / read-only
adn_list_variantsList org delivery variantsread-only

Resources

The server also exposes canonical docs as MCP resources for clients that attach context directly: audiodn://openapi.json, audiodn://llms-full.txt, and audiodn://guide/{topic} for each guide.

Example flow

An agent helping a user host a podcast might call:

  1. adn_get_guide({ topic: "upload" }) — learn the canonical multi-step flow.
  2. adn_create_collection({ title: "My Podcast" })
  3. adn_create_upload_session({ collection_id })
  4. adn_create_track_in_upload_session({ upload_session_id, file_name: "ep1.mp3" })
  5. Your code PUTs the audio bytes to track_upload.upload_url.
  6. Poll adn_get_track({ track_id }) until track_status_id === "ready".
  7. adn_create_play_session({ scope: "track", track_id }) — returns a signed playback URL that can be embedded directly.

Build from source

bash
npm installnpm run buildnpm test           # vitestnpm run smoke      # build + spawn the real binary over stdionode dist/index.js

Deploy the hosted endpoint

The Cloudflare Worker in worker/ serves the same tools over Streamable HTTP.

bash
npx wrangler loginnpm run dev:worker        # local: http://localhost:8787/mcp and /healthnpm run deploy            # publish -> https://mcp.audiodelivery.net (custom domain)curl https://mcp.audiodelivery.net/health

The custom domain mcp.audiodelivery.net is provisioned by Cloudflare from the routes entry in wrangler.toml (the audiodelivery.net zone must be on the same Cloudflare account).

To list on the official MCP registry (registry name net.audiodelivery/mcp, which must match mcpName in package.json): verify the domain once with mcp-publisher login dns --domain audiodelivery.net (add the printed TXT record), confirm remotes[0].url in server.json points at the deployed URL, then mcp-publisher publish.

Keeping docs fresh

Bundled snapshots live in assets/snapshots/. Refresh them from the public site with npm run sync; prepublishOnly verifies they are consistent before a release.

Reference

Source: README.md at commit f20f46e

Tools

6

adn_about

About this server

Report the MCP server version, the bundled OpenAPI version, the docs source (bundled snapshot vs live), and the canonical API base URL. Use this to confirm how fresh the grounded documentation is.

Takes no parameters.

adn_search_docs

Search docs

Search the bundled AudioDN documentation (llms-full.txt, OpenAPI operation summaries, and guides) for a keyword or phrase. Returns ranked snippets. Use this before writing integration code to ground answers in canonical docs.

Parameterslimitqueryrequired

adn_list_operations

List API operations

List every AudioDN REST API operation from the bundled OpenAPI spec (operationId, method, path, summary). Use this to discover the exact, canonical endpoints instead of guessing.

Takes no parameters.

adn_get_operation

Get API operation

Get the full OpenAPI definition for a single operation by operationId (method, path, parameters, request body, responses). Use adn_list_operations to find operationIds.

ParametersoperationIdrequired

adn_get_guide

Get guide

Get a concise, canonical guide for a core AudioDN concept. Topics: authentication, upload, processing, playback, webhooks, variant-types, security, compatibility.

Parameterstopicrequired

adn_list_variant_types

List variant types

List the AudioDN variant types (transcode, preview, levels, waveform_video, waveform_image, original, cover) with descriptions and whether each can be created via the REST API. Use this to distinguish variant types from org delivery "index" values (see adn_list_variants).

Takes no parameters.

Version history

1
  1. v0.3.3LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts