MCP server

The AudioDN Model Context Protocol (MCP) server lets AI coding assistants call the AudioDN REST API and look up canonical endpoints from bundled OpenAPI and docs — instead of guessing.

Development and automation interface

MCP is one of the integration approaches for building with AudioDN. It does not replace your application’s upload, processing, or playback interfaces — the resulting product still uses AudioDN APIs, components, and credentials as usual.

Connect

Hosted OAuth (recommended), legacy API key headers, local stdio, and client configs for Cursor, Claude, VS Code, and Codex.

Open connect guide →

Tools & resources

Knowledge tools, live API tools (including output presets), MCP resources, and a short agent workflow.

Open tools reference →

Two connection modes

Mode	Config	Knowledge tools	Live API tools
Hosted (recommended)	`https://mcp.audiodelivery.net/mcp` (Streamable HTTP)	Require auth (OAuth or legacy key)	Same — full tool set when authenticated
Local stdio	`npx -y @audiodn/mcp`	No key required	Need `ADN_API_KEY` (API Access)

Prefer the hosted URL with no pasted key: your client runs OAuth, you sign in at account.audiodeliverynetwork.com, pick an organization, and Allow. Consent mints a revocable API Access key labeled MCP · … under Settings → API Keys. Delete that key to disconnect.

Safety model

Reads and knowledge tools are annotated read-only.
Create/update tools are annotated so MCP clients can prompt for approval.
Delete tools (adn_delete_creator, adn_delete_collection, adn_delete_track) are available whenever live API tools are authenticated. They set destructiveHint: true — clients should confirm before running them.

Package & registry

npm: @audiodn/mcp (npx -y @audiodn/mcp)
Official MCP registry name: net.audiodelivery/mcp
Hosted health/info: https://mcp.audiodelivery.net/health

Build with AI — interactive walkthrough to connect MCP and start a feature.
For AI agents — Agent Kit (available) and agent-oriented reference. AI Plugin is coming soon.
Integrations — choose Web Components, REST, MCP, or webhooks.
API reference — REST endpoints the live MCP tools call.