AudioPod AI (core)

ai.audiopodPublished by audiopod.aiOfficial publisherv2026.10.14Updated Nov 4, 2026

Transcribe with speaker labels, split stems, remove noise, separate speakers, convert audio to MIDI.

The publisher's own server: AudioPod AI

VerifiedStreamable HTTPWeb executableMedia & DesignAI & ML

Overview

AI-generated overview

Hosted AudioPod audio AI server that lets an assistant transcribe, split stems, denoise, separate speakers and convert audio to MIDI over a remote endpoint.

What you can do
  • Transcribe audio with word-level timestamps, speaker labels and SRT/VTT subtitles
  • Split tracks into stems (vocals, drums, bass) or isolate each speaker on its own track
  • Remove background noise and convert audio/video formats or recordings to MIDI
  • Poll long-running jobs and check account credits or the connected profile
When to use it
Useful when an assistant needs to process existing audio or video files — meeting or interview transcripts, karaoke or stem extraction, cleanup of noisy recordings, or MIDI conversion — without running local models or a GPU.
Requirements
A remote streamable-HTTP endpoint; no install or local runtime. Authentication is OAuth 2.1, with a sign-in window on first use, or an X-API-Key header for headless and CI use. Network access is required.
Before you install
The core endpoint only works on audio you already have; the full endpoint adds tools that create new audio. Long-running jobs return a job_id that must be polled. An API key is a secret and should be kept out of shared configs. Uploaded audio is processed by a third-party hosted service.

Installation

In SourceWeft

  1. Open AudioPod AI (core) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/ai.audiopod%2Faudiopod-core/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "audiopod-ai-core": {
      "type": "http",
      "url": "https://mcp.audiopod.ai/core"
    }
  }
}

README

AudioPod MCP Server

Hosted Model Context Protocol server for AudioPod's audio AI. Give any MCP-capable agent — Claude Desktop, Claude Code, Cursor, Continue, Cline, Goose, Codex — audio tools over a remote endpoint. No install, no local models, no GPU.

Full endpointhttps://mcp.audiopod.ai — 18 tools: transcription, stems, noise removal, speakers, MIDI, conversion, speech, voices and music
Core endpointhttps://mcp.audiopod.ai/core — 9 tools that work on audio you already have; none creates new audio
TransportStreamable-HTTP (MCP 2025-06-18)
AuthOAuth 2.1 — your client opens a sign-in window on first use. For CI / headless use, send X-API-Key: ap_* instead (get a free key)
Docshttps://docs.audiopod.ai/agents · MCP reference https://docs.audiopod.ai/sdks/mcp
Discovery/.well-known/mcp/server-card.json

Registry names (official MCP Registry): ai.audiopod/audiopod (full, server.json) and ai.audiopod/audiopod-core (core, server-core.json).

Installing with an agent? llms-install.md is the unattended-install guide — config for each client, how to verify, and the failures to expect.

Using a coding agent? AudiopodAI/audiopod-plugins wraps this server plus fourteen task skills as a one-command install for the major agent CLIs and editors.

Prefer HTTP? The same capabilities are a REST API, and the public Getting Started collection reaches a real 200 in two requests with no account and no API key. More about the collections.

[Run in Postman]

Tools

ToolEndpointDoes
transcribe_audiofull, coreTranscribe with word-level timestamps, speaker labels and SRT/VTT subtitles
separate_stemsfull, coreSplit a track into stems (vocals, drums, bass, …); two-stem mode = karaoke
denoise_audiofull, coreRemove background noise while preserving voice character
separate_speakersfull, corePut each speaker on their own track
convert_mediafull, coreConvert audio/video formats (mp3/wav/flac/ogg/m4a, mp4/mov)
audio_to_midifull, coreConvert a recording to MIDI
check_job_statusfull, corePoll the status/result of a long-running job (free)
get_accountfull, coreCheck account and credits
get_profilefull, coreIdentify the connected account
text_to_speechfullSpeech in 200+ languages, 500+ voices and custom clones
clone_voicefullClone a voice (200+ languages) from a 5–30s reference clip, with consent
change_voicefullConvert a recording to a different target voice
generate_musicfullSongs, instrumentals, rap, or vocal stems from a text prompt
compose_musicfullCompose a song score
revise_music_scorefullRevise a song score
record_music_scorefullRecord a song score to audio
get_music_scorefullRead a song score
edit_music_scorefullDeprecated alias of revise_music_score

Long-running tools return a job_id; poll with check_job_status.

Add it

Claude Code (OAuth sign-in on first use; swap in /core for the core endpoint)

bash
claude mcp add --transport http audiopod https://mcp.audiopod.ai --scope user

Claude Desktop / Cursor / Continue / Cline — add to your mcpServers config:

json
{  "mcpServers": {    "audiopod": { "url": "https://mcp.audiopod.ai" }  }}

Headless / CI — skip OAuth with an API key header:

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

Try it (raw JSON-RPC)

bash
# List toolscurl -s 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"}'
# Text to speechcurl -s https://mcp.audiopod.ai \  -H "X-API-Key: ap_YOUR_KEY" -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",       "params":{"name":"text_to_speech","arguments":{"text":"Hello from my agent."}}}'

Building a startup on this?

Apply to AudioPod for Startups — free Pro for 3 months plus developer API credits for eligible early-stage teams.

Links

Three manifests live here and they are not interchangeable: server.json and server-core.json are the official registry entries (registry schema) for the full and core endpoints, server-card.json is the MCP server card — a reference copy, since the live card is served at the Discovery URL above.

License

MIT — see LICENSE. (Covers this listing/README; the AudioPod service itself is governed by the AudioPod Terms.)

Source: README.md at commit 549eaa6

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2026.10.14LatestOct 14, 2026

Score

85% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Audiopod integrations