Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Podcast MCP

No user-submitted related servers found.

    Related Servers

    • Audionaut MCP Server

      kvoltmer
      F
      license
      A
      quality
      A
      maintenance
      MCP 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 audionau
      22
      245
      -

    • Ardour Ultra MCP

      Elias02345
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      GPL 3.0

    • PampaPilot MCP Server

      LeoLisena
      F
      license
      A
      quality
      B
      maintenance
      MCP 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
      -

    • REAPER MCP Server

      shiehn
      A
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      83
      MIT

    • reaper-mcp

      vecnode
      A
      license
      B
      quality
      D
      maintenance
      This 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.
      40
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.7/5.0

    Scored across 160 tools

    Disambiguation2/5

    Several clusters overlap heavily (cut_time_range vs ripple_delete vs strip_silence; correct_transcript vs apply_transcript_cleanup vs reconcile_transcript; multiple speaker_* and play_* tools), and many tools have empty descriptions, so an agent cannot reliably pick the right one. The few descriptive entries (e.g. preview_inaudible_cut vs suggest_handoff_cut) show the set can disambiguate, but most tools lack that clarity.

    Naming Consistency2/5

    Names mix noun_verb patterns (track_add, history_undo, pipeline_run) with verb_noun patterns (add_effect_tool, list_clips_tool, create_review_share_tool), and the _tool suffix is applied inconsistently (track_remove_tool vs track_add, add_comment vs delete_comment_tool). This makes the naming pattern unpredictable even though everything is lower_snake_case.

    Tool Count1/5

    160 tools is an extreme count for a single MCP server and far beyond the 3-15 well-scoped range. The surface could be split into focused sub-servers (editing, transcript, review, recording, session) or consolidated into compound operations; as-is it will overwhelm context and selection.

    Completeness4/5

    The tool surface is exceptionally broad for podcast production—ingest, transcription, editing, mixing, review, history, session control, recording, and social clips are all covered. Minor gaps remain (e.g., episode lifecycle is only episode_create, no track listing, no effect parameter updates), but agents can usually work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources