Podigee Unifies Podcast Production—but Its AI Control Is Still Early Access

|Author: QUASA Editorial Team|5 min read| 2
Podigee Unifies Podcast Production—but Its AI Control Is Still Early Access

On September 30, 2026, Berlin-based Podigee launched a redesigned platform that brings browser recording, hosting, audio and video distribution, repurposing and analytics into one podcast workflow. Podigee’s launch announcement says its existing MCP connection had been limited to analytics and that expanded AI-assistant control will reach accounts gradually through a waitlist; co-founder and CEO Mateusz Sójka expressed the open-tool principle as “The feed belongs to the podcasters.”

The release gives producers a path from recording to episode preparation and publication within Podigee, subject to their plan’s features. A recording can become an episode and transcript, with the transcript supplying material for titles, descriptions, show notes, chapters and short-form content. Managing those tasks from an AI assistant has a different availability status: the expanded MCP connection is in early access.

One recording feeds audio and video publication

Podigee’s recording studio lets remote guests join through a browser link without installing separate software. Each participant’s audio and video are captured locally, and the recording becomes an episode in the platform. For a team that currently records in one service and hosts in another, this removes a file transfer between two stages of production, provided its plan includes the studio.

The transcript then becomes working material for episode metadata and other content. Titles, descriptions, show notes and chapter markers can be prepared alongside quotes, short videos, audiograms, newsletter text and article drafts. Those outputs still need editorial decisions: a producer chooses which suggestions to use, checks that a quote represents its speaker and adjusts a clip before publishing it.

Audio and video use the same episode workflow. Podigee can generate an audio track for a conventional podcast feed from a video recording while keeping the episode’s metadata together. Episodes can reach Spotify, Apple Podcasts, YouTube, Amazon Music and Deezer from the platform. Submission still varies by destination: Podigee handles some directly, while others require the publisher to finish the process on the destination platform.

Which parts of a podcast stack can move to Podigee now

The Podigee plan comparison puts the Recording Studio in GROW, listed at €29 per month before any applicable VAT, and higher tiers; automatic directory export is included in paid plans, while multi-person team access starts at SCALE, listed at €39 per month. Analytics is available on every plan, but its history ranges from seven days on the free LAUNCH tier to complete history on CREATOR. Video allowances also vary by plan.

  • Browser recording — available with a plan gate. On GROW and higher tiers, the studio can replace a separate remote recording service for conversations captured in the browser. Guests join by link, and the resulting recording moves into episode preparation.
  • Hosting and distribution — available. Podigee can replace a separate podcast host and reduce repeated publishing work through its feed and connected destinations. Automatic directory export requires a paid plan, and some directory submissions still need action outside Podigee.
  • Transcripts and repurposing — available in the platform. Episode transcripts, metadata preparation, clips and text drafts can reduce reliance on separate transcription and drafting tools. The producer retains the decision over what is edited and released.
  • Podcast analytics — available, with plan-dependent history. Reporting for hosted shows can replace a basic standalone podcast dashboard. The length of history a team can inspect depends on its subscription.
  • Expanded AI control through MCP — early access. The planned production controls could move episode management and publication preparation into a compatible assistant, but access is being enabled gradually through a waitlist.

Analytics joins reports without treating every metric alike

The redesigned analytics view brings shows into one overview and displays Podigee’s podcast figures alongside Spotify and YouTube data. Each metric identifies its source. That matters when a studio reports on an episode across audio and video: a host-measured download and a platform’s viewing figure can appear in the same workspace while retaining their different meanings.

Podigee’s podcast analytics is independently certified under the IAB Podcast Measurement Guidelines. The certification concerns its podcast measurement, rather than every figure supplied by Spotify or YouTube. A network may be able to retire a dashboard used mainly to gather those figures, but reporting across platforms still requires the team to preserve the definition and source of each measure.

MCP access is the remaining production boundary

The expanded MCP connection is intended to let compatible assistants work with podcasts and episodes, transcripts, analytics and publication preparation through account permissions. Claude, Codex and other compatible MCP clients are named as connection options. An assistant could therefore handle more of the routine work around an episode, but a place on the waitlist does not grant those production controls immediately.

Bringing recording, hosted files, metadata, distribution and reporting under one provider also concentrates a studio’s operational dependence on that provider. Podigee’s RSS feeds, API and integrations leave room to connect outside tools, so consolidating the workflow need not mean moving every production task into the same account. Until expanded MCP access reaches a team, its assistant-led production work remains separate from the recording and publishing functions already available in Podigee.

Also read:

Share:

Subscribe to our newsletter

Get the latest Web3, AI, and crypto news delivered straight to your inbox.

0