Podcastindex MCP logo

Podcastindex MCP

by conorbronsdon

Read-only MCP tools for searching, inspecting, and monitoring podcasts through the Podcast Index API.

Install Podcastindex MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.transistor.fm

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

conorbronsdon/podcastindex-mcp MCP server connects MCP clients to the Podcast Index API for podcast, episode, feed, trend, and value4value lookups. It exposes read-only tools for searching by person, term, or title; resolving feeds and episodes; checking live and recent activity; and retrieving feed health and statistics. Node.js 18+ and Podcast Index API credentials are required. Reach for it when an agent needs public podcast discovery or research data rather than publishing or analytics controls.

Use cases

  • Find episodes featuring a person as a host or guest
  • Search podcasts by topic, title, or keyword
  • Check podcast feed metadata and health
  • Monitor trending, live, recent, or newly added shows
  • Inspect value4value payment information

Key features

  • Read-only Podcast Index API access
  • Search by person, term, and podcast title
  • Podcast and episode lookup by multiple identifiers
  • Trending, live, recent, and newly indexed content discovery
  • Feed health, category, statistics, and value4value queries
  • Typed handling for authentication, rate-limit, validation, not-found, and server errors

Tools18

What Podcastindex MCP lets your agent do. Expand a tool for its parameters.

Self-reported~355 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 59d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit10d agoMost recent push to the default branch.
Tools exposed18Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Podcastindex MCP works

What conorbronsdon/podcastindex-mcp MCP server does

conorbronsdon/podcastindex-mcp MCP server exposes the Podcast Index API through read-only MCP tools. It can find episodes featuring a particular person, search indexed podcasts by topic or keyword, and locate shows by title. It also resolves podcasts through RSS feed URLs, Podcast Index feed IDs, Apple Podcasts IDs, or podcast:guid values.

The server covers discovery and inspection tasks across the index. Agents can retrieve a podcast's metadata, categories, update information, and feed health; list episodes for a feed; inspect an individual episode; and find currently live, recently published, recently updated, or newly added content. Additional tools return trending podcasts, category IDs, value4value payment details, and current aggregate Podcast Index statistics.

How it works

Each MCP tool is a thin wrapper around a Podcast Index API operation. The server communicates over the standard local process configuration shown for MCP clients, while the API supplies the underlying podcast and episode data. All exposed tools are marked read-only, so calls do not change podcasts, feeds, episodes, or account data.

Search tools support different discovery paths: search_by_person finds appearances where someone was a host or guest, search_by_term performs full-text discovery, and search_by_title searches podcast names. Lookup tools accept identifiers appropriate to the selected endpoint, including feed URL, feed ID, iTunes ID, GUID, or episode ID.

API failures are returned as MCP error responses. Internally, the project distinguishes authentication, rate-limit, validation, not-found, and server failures so error messages can identify the type of problem rather than reporting only a generic API failure.

Setup and configuration

Running conorbronsdon/podcastindex-mcp requires Node.js 18 or newer and free Podcast Index API credentials. The repository setup flow is:

  1. Clone the repository.
  2. Run npm install.
  3. Run npm run build.
  4. Start the compiled build/index.js from the MCP client's server configuration.

Set these environment variables in the client configuration:

  • PODCASTINDEX_API_KEY
  • PODCASTINDEX_API_SECRET

Both launch the built Node.js entry point and pass the credentials through the server environment.

Tools and capabilities

The available tool groups include:

  • Person, term, and title search across indexed podcasts.
  • Podcast lookup by feed URL, feed ID, Apple Podcasts ID, or GUID.
  • Trending podcasts with optional language and category filters.
  • Episode lists by feed, individual episode lookup, and live episode discovery.
  • Recent episodes, recently updated feeds, and newly indexed feeds.
  • Value4value information by feed ID or feed URL.
  • Podcast Index category listings and current aggregate statistics.

These capabilities fit research workflows such as locating guest appearances, finding shows by subject, checking whether a feed is healthy, reviewing a show's recent episodes, or examining current directory trends. They do not provide publishing, editing, or analytics-management operations.

Limitations and notes

conorbronsdon/podcastindex-mcp MCP server depends on the availability, coverage, rate limits, and response behavior of the Podcast Index API. API credentials are required even though the project uses the free API access described in its prerequisites. Results shown in the repository's demonstration are sample data, not guaranteed live responses.

The server is intentionally read-only. It cannot publish episodes, modify feed metadata, manage podcast accounts, or provide platform-specific listener analytics. The repository is an independent project and is not affiliated with, sponsored by, or endorsed by the Podcast Index.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Podcastindex MCP

conorbronsdon/podcastindex-mcp is an MCP server that connects AI clients to the Podcast Index API. Its main tools search podcasts and guest appearances, retrieve podcast and episode metadata, inspect feed health, find trending or recent content, and query categories, statistics, and value4value information. All tools are read-only.

Install it by cloning the repository, running `npm install`, and building with `npm run build`. The server requires Node.js 18 or newer. Configure your MCP client to launch `build/index.js` with the required Podcast Index credentials in its environment.

It needs `PODCASTINDEX_API_KEY` and `PODCASTINDEX_API_SECRET`. Obtain the credentials from the Podcast Index API service, then pass both variables in the MCP server configuration used by your client.

Yes, Claude Desktop is documented as a supported client. Add an MCP server entry that runs the built Node.js file and supplies `PODCASTINDEX_API_KEY` and `PODCASTINDEX_API_SECRET` through the entry's `env` object.

No. The server is entirely read-only, and its tools are marked with `readOnlyHint: true`. It can search and retrieve Podcast Index data, but it does not publish episodes or mutate podcast, feed, or account information.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPodcastindex MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/conorbronsdon-podcastindex-mcp?style=directory)](https://allmcps.com/mcp/conorbronsdon-podcastindex-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/conorbronsdon-podcastindex-mcp"><img src="https://allmcps.com/api/badge/conorbronsdon-podcastindex-mcp?style=directory" alt="Podcastindex MCP on AllMCPs" /></a>