Apple Podcasts MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPLE_PODCASTS_VENDOR_ID | Yes | Your Apple Podcasts vendor number, digits only (e.g., '87654321'). Found under Settings in Apple Podcasts Connect. | |
| APPLE_PODCASTS_ACCOUNT_ID | No | Optional account number required only if your token has access to more than one Apple Podcasts account (Reporter error 214). | |
| APPLE_PODCASTS_ACCESS_TOKEN | Yes | Your Apple Podcasts Connect access token. Generate one in Apple Podcasts Connect > Settings > Access Token. Tokens expire after 180 days. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apple_podcasts_check_accessA | Verify the configured Apple Podcasts Connect credentials and list the vendor numbers this access token can read. Run this first, and run it whenever another tool reports an auth failure: Reporter access tokens expire 180 days after they are generated, and the failure looks like a permissions problem rather than an expiry. Returns no listening data. |
| apple_podcasts_summaryA | Show-level listening summary from Apple Podcasts Connect over a date range: plays, unique listeners, engaged listeners, and followers, per period and totalled. Apple aggregates listening from unique devices, so listener counts are devices, not people, and an engaged listener is a device that played at least 20 minutes or 40% of an episode. This is the owner-side data Apple's hosting APIs do not expose. Use it for 'how is the show doing on Apple' questions. Keep the range short; each period is a separate call to Apple. |
| apple_podcasts_episodesA | Per-episode listening from Apple Podcasts Connect over a date range: plays, unique listeners, and engaged listeners for each episode, rolled up across the range and ranked. Answers 'which episodes held attention on Apple'. Apple aggregates from unique devices, so these are device counts, not headcounts, and an engaged listener is a device that played at least 20 minutes or 40% of an episode — a depth threshold, not a completion. Takes an explicit date range and a row cap; both are required to keep the response bounded. |
| apple_podcasts_followersA | Follower trend for the show on Apple Podcasts over a date range: one value per period plus the change across the window. Use it for 'is my Apple following growing'. Read the resolvedColumn field in the response before interpreting the numbers: Apple's follower column has been both a running total and a per-period count, and which one you get changes what 'change' means. |
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 4 tools
Each tool has a clearly distinct purpose: check_access verifies credentials, summary provides show-level metrics, episodes provides per-episode metrics, and followers provides follower trends. There is no overlap or ambiguity between them.
All tool names follow the consistent pattern 'apple_podcasts_<resource>', making it highly predictable and easy to understand the target of each call. Even though 'check_access' uses a verb-noun structure, it fits the same prefix convention.
With just 4 tools, the server is tightly scoped to the core analytics operations needed for Apple Podcasts Connect: access verification, show summary, episode breakdown, and follower trends. Each tool earns its place with no redundancy.
The tool set covers the primary analytics surface for a podcast show on Apple: overall performance, per-episode performance, and audience growth. The access check tool ensures credential management, and the provided date-range and row-cap parameters cover typical use cases. No obvious gaps for the stated domain.