Skip to main content
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 with two tool sets: the full set at https://mcp.audiopod.ai and a core set for audio you already have at https://mcp.audiopod.ai/core. New to agents? Start with AudioPod for AI agents.

Endpoint

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

Tools exposed

Schemas are returned by tools/list — these are the names and one-liners: The core endpoint (https://mcp.audiopod.ai/core) serves only transcribe_audio, separate_stems, denoise_audio, separate_speakers, convert_media, audio_to_midi, check_job_status, get_account and get_profile: tools that work on audio you already have and never create new audio. Scopes are enforced when authenticating with an API key. JWT-based auth implies full user privileges. Not sure which music tool to use? See Choosing how to make music.

Setup

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:
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 tools.

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):
Restart Claude Desktop. Try: “Generate a 30-second lo-fi instrumental for studying.”

JSON-RPC examples

Initialize

List tools

Call a tool

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:
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

  1. Re-check your config file path — most agents won’t reload after edits without a restart.
  2. Confirm the URL is exactly https://mcp.audiopod.ai (no trailing slash, no /sse).
  3. Hit the discovery URL: curl https://mcp.audiopod.ai returns a small JSON descriptor when the proxy is healthy.
  • Verify your key starts with ap_.
  • Check the key’s scopes — the dashboard shows the per-tool scopes granted.
  • For wildcard access use scope *.
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

The same 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.