PodHome MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PODHOME_SHOWS | Yes | JSON string mapping show slugs to API keys. Example: {"my-main-podcast": "phk_abc123...", "weekly-tech-show": "phk_xyz789..."} | |
| PODHOME_BASE_URL | No | Base URL for the API (default: https://serve.podhome.fm) | https://serve.podhome.fm |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_showsB | List all configured Podhome show slugs. |
| create_episodeA | Create a new episode for a specific show. Args: show: One of the slugs configured in PODHOME_SHOWS (e.g., "my-main-podcast") file_url: Publicly accessible URL to the media file title: Episode title description: Optional episode description (can contain HTML) link: Optional canonical link for the episode publish_date: UTC ISO-8601 future date to schedule publishing use_podhome_ai: Run Podhome AI to generate transcript and artifacts suggest_chapters: Generate chapters (requires use_podhome_ai=true) suggest_details: Generate description and title suggestions suggest_clips: Generate clips (requires use_podhome_ai=true) enhance_audio: Run audio enhancement (paid feature) |
| list_episodesC | List episodes for a specific show. Args: show: One of the slugs configured in PODHOME_SHOWS status: Optional status filter (0-5) include_transcript: Include transcript in response include_chapters: Include chapters in response include_downloads: Include download counts include_people: Include people in response |
| schedule_episodeB | Schedule or publish an episode. Args: show: One of the slugs configured in PODHOME_SHOWS episode_id: The ID of the episode to schedule publish_now: Publish immediately publish_date: Future UTC ISO-8601 publish date |
| modify_episodeC | Modify an episode's metadata. Args: show: One of the slugs configured in PODHOME_SHOWS episode_id: ID of the episode to modify title: New episode title description: New description (can contain HTML) episode_nr: Episode number season_nr: Season number image_url: Image URL image_data: Base64 encoded image data |
| create_clipB | Create a clip (soundbite) from an episode. Args: show: One of the slugs configured in PODHOME_SHOWS episode_id: ID of the episode to clip title: Title of the clip start_time: Start time in seconds (can be fractional) duration: Duration in seconds (can be fractional) |
| list_webhooksB | List all registered webhooks for a specific show. Args: show: One of the slugs configured in PODHOME_SHOWS |
| register_webhookB | Register a new webhook. Args: show: One of the slugs configured in PODHOME_SHOWS url: Webhook endpoint URL action_type: Action type - "episode_published" or "episode_live" |
| delete_webhookC | Delete a webhook. Args: show: One of the slugs configured in PODHOME_SHOWS integration_id: The ID of the webhook to delete |
| test_webhookC | Test webhooks. Your webhook is called with data from the latest published or live episode. Args: show: One of the slugs configured in PODHOME_SHOWS integration_id: Optional specific webhook ID to test |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose targeting specific resources and actions: create_clip, create_episode, delete_webhook, list_episodes, list_shows, list_webhooks, modify_episode, register_webhook, schedule_episode, and test_webhook. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern (e.g., create_clip, list_episodes, modify_episode) with clear, descriptive verbs and nouns. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 10 tools, the count is well-scoped for podcast management, covering key operations like episode and clip creation, listing, modification, scheduling, and webhook handling. Each tool serves a distinct and necessary function without redundancy or bloat.
The tool set provides comprehensive coverage for podcast management, including CRUD operations for episodes and webhooks, plus scheduling and AI features. A minor gap is the lack of a delete_episode tool, but agents can work around this using modify_episode or other methods, and core workflows are well-supported.