Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Podcast transcripts: send an episode link and get the transcript back, a page at a time.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AUDIVO_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.audivo.dev/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"audivodotdev": {
"command": "npx",
"args": [
"-y",
"@audivo/mcp"
],
"env": {
"AUDIVO_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http audivodotdev https://api.audivo.dev/mcpclaude mcp add audivodotdev --env AUDIVO_API_KEY=your-value -- npx -y @audivo/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"audivodotdev": {
"url": "https://api.audivo.dev/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"audivodotdev": {
"command": "npx",
"args": [
"-y",
"@audivo/mcp"
],
"env": {
"AUDIVO_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"audivodotdev": {
"type": "http",
"url": "https://api.audivo.dev/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"audivodotdev": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@audivo/mcp"
],
"env": {
"AUDIVO_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.audivo.dev/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account AudivoDotDev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: AUDIVO_API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.4.2) reached the registry 35 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Podcast transcripts for Claude, ChatGPT, Codex, Cursor, and any other MCP client, backed by the Audivo API. Ask for an episode; get the transcript back.
Transcribe the latest episode of Acquired and summarise it.
Two ways to connect. The hosted endpoint serves eleven tools. The local server serves the same eleven, with transcribe also taking a file on your machine or a YouTube link, plus upload_audio and youtube_search. Both serve an app to clients that render MCP Apps.
| Hosted | Local | |
|---|---|---|
| Where it runs | Audivo's servers | Your machine, spawned by the client |
| Transport | Streamable HTTP at https://api.audivo.dev/mcp | stdio via npx -y @audivo/mcp@latest |
| Credential | Sign in with OAuth, or Authorization: Bearer hk_live_… | AUDIVO_API_KEY environment variable |
| Good for | Claude on the web and desktop, ChatGPT, anything that takes a URL | Claude Code, Codex, Cursor, VS Code, and every client that spawns a process |
| YouTube | No | Yes, downloaded on your machine with yt-dlp |
| Tool | What it does | Spends credits |
|---|---|---|
transcribe | The default. One episode in, its transcript out, a page at a time | Yes, about one per audio minute |
search_shows | Find shows by name, host, or topic | No |
chart_shows | The current chart for a category | No |
list_episodes | A show's episodes, newest first | No |
quote | Price a selection of many episodes before anything runs | No |
confirm | Turn a quote into a job group | Yes, up to the quote's ceiling |
group_status | Where a group's jobs are, and which transcripts are ready | No |
list_groups | Your recent groups | No |
cancel_group | Stop what has not started and release its credits | No |
read_transcript | A job's transcript, a page at a time; waits for a running job | No |
list_transcripts | Your recent transcripts, with their titles | No |
upload_audio | Announce and upload a file from this machine | No (local only) |
youtube_search | Find an episode on YouTube when it has no podcast feed | No (local only) |
transcribePass one episode: an Apple Podcasts link, feed_url with guid, an episode_id from list_episodes (with that show's feed_url and itunes_id, so an episode nobody has transcribed yet can be found), or an upload_id — and on the local server, a YouTube link or an absolute path.
transcribe waits for it inside the call: up to 20 seconds on the hosted server, whose gateway allows 29, and 50 by default on the local one, which reports progress to clients that ask for it. If it is still running, the answer is the job_id and read_transcript waits the rest.max_credits refuses the call, before anything is spent, if it could cost more. A job holds its ceiling (the estimate plus 25%) and settles at the audio it measured, never above.For many episodes at once — a chart, a back catalogue — use quote and then confirm, which refuses unless the model restates the quote's total.
Clients that render MCP Apps — ChatGPT, Claude, and others — show results in Audivo's own view instead of only text:
The app is one self-contained page served as ui://audivo/app-v1.html. It loads nothing from any domain, so it declares none. Its data travels in each result's _meta, which hosts give the app and never the model; the model keeps getting the same fenced text as before. Every title and transcript line is rendered as text, never as markup. Clients without MCP Apps ignore all of this.
Its source is in ui/; npm run build:ui bundles it into src/app-html.ts, and a test fails when the two disagree.
npxYou need an API key from the Audivo dashboard. Keys are shown once. Set the key in the environment the client starts the server with, then add the server.
Claude Code (or install the Audivo plugin, which adds this server and the skill together)
claude mcp add --scope user audivo -e AUDIVO_API_KEY=hk_live_... -- npx -y @audivo/mcp@latest
Codex
codex mcp add audivo --env AUDIVO_API_KEY=hk_live_... -- npx -y @audivo/mcp@latest
Cursor, Claude Desktop, Windsurf, and other JSON-configured clients
{
"mcpServers": { "audivo": { "command": "npx", "args": ["-y", "@audivo/mcp@latest"], "env": { "AUDIVO_API_KEY": "hk_live_..." } } } }
VS Code (.vscode/mcp.json)
{
"servers": { "audivo": { "type": "stdio", "command": "npx", "args": ["-y", "@audivo/mcp@latest"], "env": { "AUDIVO_API_KEY": "hk_live_..." } } } }
Keep files that contain a real key out of Git and shared chats.
@latest makes npx look the package up on npm each time the client starts the server, so a new release arrives with your next session. To get it in the session you are in, restart the server: in Claude Code, /mcp, choose audivo, then Reconnect. A spec without @latest works too, but a bare @audivo/mcp resolves to a copy in the current project first, when there is one. The hosted server at https://api.audivo.dev/mcp is kept current by Audivo.
| Variable | Required | Meaning |
|---|---|---|
AUDIVO_API_KEY | Yes | Your API key. Bearer in front of it is accepted and normalised. |
AUDIVO_API_BASE_URL | No | The API origin. Defaults to https://api.audivo.dev. Must be a public https origin: no userinfo, no loopback or private address. |
AUDIVO_YTDLP_PATH | No | A yt-dlp binary to use for YouTube, instead of one on PATH or the managed copy. |
AUDIVO_CACHE_DIR | No | Where the managed yt-dlp is kept. Defaults to your user cache directory (~/Library/Caches/audivo-mcp, ~/.cache/audivo-mcp, …). |
The server writes nothing to stdout except protocol messages. Log lines go to stderr as JSON, and the key never appears in them.
When a show has no public RSS feed — many exist only on YouTube — search_shows finds nothing. On the local server, youtube_search finds the episode and transcribe takes its link:
Find the Costco episode of Acquired on YouTube and transcribe it
transcribe downloads the video's audio on your machine with yt-dlp, audio only and with no transcoding, uploads it to Audivo as your own upload, and transcribes it. The transcript is private to your account.
yt-dlp is found in this order: AUDIVO_YTDLP_PATH; a yt-dlp on your PATH; otherwise the project's official standalone binary for your platform, downloaded once from its GitHub releases into your user cache directory and checked against that release's SHA2-256SUMS before it is made executable. The package has no install script: nothing is downloaded until the first YouTube call. A managed copy that stops working is updated to the latest release once and the call retried; a yt-dlp you installed yourself is never touched. yt-dlp is given the Node running this server as its JavaScript runtime.
You run the download, on your machine, under your own account; you are responsible for having the rights to transcribe what you download, as with any upload. Audivo's servers never fetch from YouTube, which is why the hosted server does not offer any of this.
A recording you made, an interview, or any file you already have on disk:
Transcribe /Users/alex/Downloads/interview.m4a
transcribe with path announces the file to Audivo (its hash, size, content type, and duration), uploads the bytes straight to Audivo's storage with the signed URL the announcement returns, and transcribes it. upload_audio does only the first two steps and returns an upload_id, for when you want to quote several uploads together. The path must be absolute.
Limits: 1 byte to 5 GiB, up to 10 hours, and one of these content types: audio/mpeg, audio/mp3, audio/mp4, audio/m4a, audio/x-m4a, audio/aac, audio/x-aac, audio/ogg, audio/opus, audio/flac, audio/x-flac, audio/wav, audio/x-wav, audio/webm. An upload is kept for 7 days, and its transcript is private to your account; each account may hold up to 10 GiB across 100 unexpired uploads at a time. See the uploads guide.
| Setting | Value |
|---|---|
| MCP URL | https://api.audivo.dev/mcp |
| Transport | Streamable HTTP
Only the beginning is shown; read the rest in the repo