Podcast MCP
Related Servers
Alternatives to Podcast MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically edit, analyze, and export audio projects through MCP tools, including multi-track editing, effects, transcription, and semantic search.1-
- FlicenseAqualityAmaintenanceMCP server for Audionaut, a free, open-source multitrack audio editor for macOS, Windows and Linux. Agents can split and move clips, set gain, fades and crossfades, time-stretch, work with regions, run audio analysis and Auto Edit, separate stems and export. When the project is open in the app, each edit lands there as one undo step and the project file is never overwritten. Setup: npx -y audionau23272-
- AlicenseCqualityBmaintenanceEnables MCP agents to inspect and precisely edit a running Ardour session — tracks, buses, groups, mixer, transport, regions, internal MIDI, plugins, routing and automation — through the DAW's Lua APIs with optional native OSC, plus offline audio analysis and comparison of master exports. Edits are exposed as 80 typed tools with persistent IDs, explicit units, preflight validation and structured change/error results.80GPL 3.0
- FlicenseAqualityDmaintenanceMCP server for controlling REAPER digital audio workstation from natural language. It enables AI agents to create tracks, import audio, adjust mix parameters, and manage sessions through typed operations and a REAPER bridge.22-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that exposes REAPER digital audio workstation functionality through a clean API interface, enabling programmatic control of 169+ REAPER operations across track management, MIDI editing, effects, automation and more.91MIT
- AlicenseBqualityDmaintenanceThis MCP server enables AI assistants to control a live REAPER DAW instance, including transport, tracks, FX, MIDI, media, markers, rendering, and project state, with an escape hatch for arbitrary ReaScript commands.40MIT
TDQS
Scored across 218 tools
Descriptions work unusually hard to draw boundaries (e.g. "prefer set_clip_join_tool over set_join_mode_tool", "not preview_inaudible_cut_tool", "use ripple_delete_tool instead"), which rescues many pairs. However, at 218 tools there are large near-duplicate families — five `cut_*` staging tools, `ripple_delete_tool` vs `ripple_delete_text_tool` vs `delete_clips_tool` vs `propose_range_cut_tool`, `propose_edits`/`apply_edits`/`approve_edits_tool`/`apply_suggested_actions_tool`, and singular/plural pairs like `set_clip_fade_tool` vs `set_clips_fade_tool` — so misselection remains a real risk.
Most names are verb_noun (list_clips_tool, add_chapter_tool, render_preview), but the `_tool` suffix is applied inconsistently across the set: `propose_edits`, `apply_edits`, `history_undo`, `feed_read`, `record_stop_tool`, `get_transcript`, `export_transcript` coexist with `*_tool` variants of the same families. Some families also mix prefixes (history_undo vs history_status_tool, track_add vs track_add_empty_tool), which is readable but not predictable.
218 tools for a single podcast-production server is a severe mismatch against the 3-15 guidance; an agent cannot hold this surface in context or discover the right tool reliably. Even though the domain is genuinely broad, the count is well past any reasonable scoping, and several tools are marginal variants of each other.
Coverage is exhaustive for the domain: ingest/recording rooms, transcription and word-level correction, gating/bleed/audibility, cut and ripple editing, fades/joins/gain, effects, rendering and export, chapters, comments/review, review shares, feeds, segment and kit libraries, social clips, speakers, history/undo, and config. Nearly every lifecycle (create/read/update/delete/undo) has an operation, with few dead ends.