MCP Server - AudioPod AI

What is MCP? Model Context Protocol is an open standard that lets AI assistants (Claude Desktop, Cursor, Continue, Cline, Goose, Codex…) call external tools through a single transport. AudioPod publishes a Streamable-HTTP MCP server that exposes nine audio AI tools.

Endpoint

Field	Value
URL	`https://mcp.audiopod.ai`
Transport	`streamable-http` (MCP 2025-06-18)
Auth	`X-API-Key: ap_*` (from your dashboard) or `Authorization: Bearer <jwt>`
Discovery	`/.well-known/mcp/server-card.json` and `/.well-known/oauth-protected-resource`

Need a key? Create one in your dashboard. Free tier credits unlock the full tool surface — no card required.

Tools exposed

The server advertises nine tools. Schemas are returned by tools/list — these are the names and one-liners:

Tool	Description	Required scope
`generate_music`	Songs, instrumentals, rap, vocal stems from a text prompt.	`music:generate`
`text_to_speech`	TTS in 85+ languages with 500+ voices and custom clones.	`voice:synthesize`
`clone_voice`	Clone a voice from a 5–30s reference clip.	`voice:clone`
`separate_stems`	Up to 16 stems (vocals, drums, bass, guitar, piano, other…).	`stems:separate`
`transcribe_audio`	Word-level timestamps, speaker diarization, SRT/VTT/JSON.	`transcribe`
`denoise_audio`	Remove background noise while preserving voice character.	`audio:write`
`translate_audio`	Dub speech across 85+ languages, keep the speaker’s voice.	`audio:write`
`generate_karaoke`	Vocal-stripped instrumental + synced lyric file.	`audio:write`
`convert_media`	MP3 / WAV / FLAC / OGG / M4A / MP4 / MOV conversion.	`audio:write`

Scopes are enforced when authenticating with an API key. JWT-based auth implies full user privileges.

Setup

One-line install (recommended)

Most modern MCP hosts now register an HTTP MCP server with a single command — no manual JSON edit, no restart needed beyond the host’s normal config reload. Pick the one that matches your tool:

Claude Code
Codex CLI
Universal (mcp-remote)

claude mcp add --transport http audiopod https://mcp.audiopod.ai \
  --header "X-API-Key: ap_YOUR_KEY" --scope user

The --scope user flag installs at the user level so every Claude Code project picks up the server. Run claude mcp list to verify, then /mcp inside the TUI to see the nine tools.

codex mcp add audiopod --url https://mcp.audiopod.ai \
  --header "X-API-Key: ap_YOUR_KEY"

Verify with codex mcp list. Inside the Codex TUI, /mcp shows the connected servers and their tools.

For any MCP client that only speaks stdio (older Claude Desktop builds, Continue, Cline before they ship native HTTP support, etc.), the mcp-remote bridge spawns a stdio process that proxies to our HTTP endpoint:

npx -y mcp-remote https://mcp.audiopod.ai \
  --header "X-API-Key: ap_YOUR_KEY"

Wire it in as a stdio server in your client’s config. Useful when manual JSON is too fiddly.

Manual config (for desktop apps without a CLI)

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "audiopod": {
      "url": "https://mcp.audiopod.ai",
      "headers": {
        "X-API-Key": "ap_YOUR_KEY"
      }
    }
  }
}

Restart Claude Desktop. Try: “Generate a 30-second lo-fi instrumental for studying.”

Edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "audiopod": {
      "url": "https://mcp.audiopod.ai",
      "headers": { "X-API-Key": "ap_YOUR_KEY" }
    }
  }
}

Reload Cursor. Try: “Use audiopod to generate a 60s upbeat intro track and download it.”

Edit ~/.continue/config.json:

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "streamable-http",
          "url": "https://mcp.audiopod.ai",
          "headers": { "X-API-Key": "ap_YOUR_KEY" }
        }
      }
    ]
  }
}

Edit ~/.config/cline/cline_mcp_settings.json:

{
  "mcpServers": {
    "audiopod": {
      "url": "https://mcp.audiopod.ai",
      "transport": "streamable-http",
      "headers": { "X-API-Key": "ap_YOUR_KEY" }
    }
  }
}

Run goose configure and add a Streamable-HTTP extension:

Type:   streamable-http
URL:    https://mcp.audiopod.ai
Header: X-API-Key=ap_YOUR_KEY

Probe the server directly to confirm your key works:

curl https://mcp.audiopod.ai \
  -H "X-API-Key: ap_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'

JSON-RPC examples

Initialize

POST https://mcp.audiopod.ai
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2025-06-18",
    "clientInfo": { "name": "my-agent", "version": "0.1.0" }
  }
}

List tools

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/list"
}

Call a tool

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "generate_music",
    "arguments": {
      "prompt": "lo-fi rainy 90 BPM, soft pads",
      "duration": 60,
      "task_type": "text2music"
    }
  }
}

The response includes a structuredContent.job_id — long-running tools return a job id immediately. Poll the matching /api/v1/<service>/jobs/<id> endpoint, or call tools/call again with the jobs lookup tool wired into your CLI.

Auth flow

AudioPod publishes RFC 9728 OAuth Protected Resource Metadata so clients can discover how to authenticate:

curl https://audiopod.ai/.well-known/oauth-protected-resource

Returns the issuer, supported scopes, and the bearer-token pattern. Most agent clients use a simple X-API-Key: ap_* header — get your key in the dashboard.

Troubleshooting

Tools don't appear in my client

Re-check your config file path — most agents won’t reload after edits without a restart.
Confirm the URL is exactly https://mcp.audiopod.ai (no trailing slash, no /sse).
Hit the discovery URL: curl https://mcp.audiopod.ai returns a small JSON descriptor when the proxy is healthy.

401 Unauthorized

Verify your key starts with ap_.
Check the key’s scopes — the dashboard shows the per-tool scopes granted.
For wildcard access use scope *.

Tool calls hang

Music and stem extraction return job ids immediately and resolve over the next 30–180 seconds. Most clients display the partial result; if yours doesn’t, fall back to the REST API to poll for completion.

Next steps

Use the CLI

Same nine tools, terminal-first.

For Agents landing

Single-pane overview of every developer surface.

Get an API key

Free credits, no card required.

Read the spec

Model Context Protocol reference.

​Endpoint

​Tools exposed

​Setup

​One-line install (recommended)

​Manual config (for desktop apps without a CLI)

​JSON-RPC examples

​Initialize

​List tools

​Call a tool

​Auth flow

​Troubleshooting

​Next steps

Use the CLI

For Agents landing

Get an API key

Read the spec

Endpoint

Tools exposed

Setup

One-line install (recommended)

Manual config (for desktop apps without a CLI)

JSON-RPC examples

Initialize

List tools

Call a tool

Auth flow

Troubleshooting

Next steps