PodBox

sh.podboxPublished by podbox.shOfficial publisherv1.0.0Updated Nov 7, 2026

Agents publish audio to your private podcast feed. Listen in your podcast app.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

PodBox lets an AI agent publish audio to your private podcast feed, which you then listen to in a podcast app.

What you can do
  • Publish audio produced by the assistant to a private podcast feed.
  • Deliver episodes to a feed you subscribe to in your own podcast app.
  • No tool list is published, so the exact operations available to the assistant are not documented here.
When to use it
Useful when you want assistant-generated audio, such as summaries or narrated updates, delivered as podcast episodes you can listen to on the go rather than as files.
Requirements
A remote endpoint at api.podbox.sh over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared.
Before you install
The server requires OAuth authorization of your PodBox account, and publishing adds audio to your feed, so review what the assistant uploads before it goes out. No further details on data handling are provided.

Installation

In SourceWeft

  1. Open PodBox 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/sh.podbox%2Fpodbox/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": {
    "podbox": {
      "type": "http",
      "url": "https://api.podbox.sh/mcp/v1"
    }
  }
}

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. v1.0.0LatestNov 7, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.