PodHome

Provides multi-show MCP access to PodHome APIs, enabling episode management, clip creation, and webhook handling across configured shows.

other

GitHub Stars

other

Language

3 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "chrislas-podhome-mcp": {
      "command": "uv",
      "args": [
        "run",
        "podhome-mcp"
      ],
      "env": {
        "PODHOME_SHOWS": "{\"my-main-podcast\": \"phk_abc123def456...\", \"weekly-tech-show\": \"phk_789xyz...\"}",
        "PODHOME_BASE_URL": "https://serve.podhome.fm"
      }
    }
  }
}

You run the PodHome MCP Server to bridge PodHome’s Integration API with your MCP client, enabling multi-show support and programmatic control over episodes, clips, and webhooks from a single, configurable back end.

How to use

To use this MCP server, first ensure you have the MCP runtime available on your system. Navigate to the PodHome MCP directory, synchronize dependencies, and then start the server so your MCP client can connect. Once running, you can register the server with your MCP client (for example, OpenClaw) using the provided registration snippet. The server exposes endpoints and functions for managing episodes, clips, and webhooks across configured shows.

How to install

Prerequisites: you need the MCP runtime tooling (uv) available on your system. You should also have a working directory where the podhome-mcp project resides.

Step 1: Change into the project directory.

Step 2: Synchronize dependencies and build environment for MCP execution.

cd podhome-mcp
uv sync

Additional configuration and usage notes

Configuration is done via environment variables. The MCP server expects the following to be set before running:

- PODHOME_BASE_URL: Base URL for the PodHome API (default: https://serve.podhome.fm)
- PODHOME_SHOWS: JSON string mapping show slugs to API keys

An example of these variables in use is shown below. This config maps two shows to their respective API keys so the server can act on behalf of each show.

export PODHOME_SHOWS='{"my-main-podcast": "phk_abc123...", "weekly-tech-show": "phk_xyz789..."}'
export PODHOME_BASE_URL="https://serve.podhome.fm"

Available tools

Episodes: create_episode

Create a new episode for a specific show.

Episodes: list_episodes

List episodes for a specific show with optional filters.

Episodes: schedule_episode

Schedule or publish an episode.

Episodes: modify_episode

Modify an episode's metadata.

Clips: create_clip

Create a clip (soundbite) from an episode.

Webhooks: list_webhooks

List all registered webhooks.

Webhooks: register_webhook

Webhooks: delete_webhook

Delete a webhook.

Webhooks: test_webhook

Test webhooks.

Utility: list_shows

List all configured show slugs.

Built by

VeilStrat

AI signals for GTM teams