Back to AI Overview

Model Context Protocol (MCP)

A deep dive into how Repodify acts as a native tool for your AI agents.

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows developers to expose custom tools, databases, and APIs directly to AI models like Claude, Cursor, and Antigravity. By running the Repodify MCP server locally alongside your AI agent, you essentially "teach" the AI how to use Repodify natively.


Authentication

The Repodify MCP Server supports both modern OAuth 2.0 with PKCE and traditional API Keys.

Option A: OAuth 2.0 (Recommended)

Modern MCP clients that support browser authentication will automatically discover our OAuth endpoint and prompt you to authorize with one click.

Auth URL: https://repodify.app/oauth/authorize

Option B: Static API Key

If configuring raw JSON files or headless scripts, generate a secret key in your Settings page and pass it as a Bearer token.

Authorization: Bearer repodify_live_...

Available MCP Tools

When your agent connects to the Repodify MCP Server, it instantly gains access to the following native tools:

search_apple_podcasts

Allows the AI to silently query the global Apple Podcasts database. It returns an array of matching episodes, complete with titles, descriptions, and the raw .mp3 URLs required to build a feed.

"Find me 10 recent episodes about quantum physics."

create_repodcast

Instructs Repodify to spin up a brand new RSS feed. The AI passes a title and description, and the server returns the unique slug required to push episodes to it.

"Create a new podcast feed called 'My Physics Playlist'."

add_episode_to_repodcast

Pushes a specific audio URL into a Repodcast feed. By stringing this together with the search tool in a loop, the AI can construct massive, thematic playlists entirely autonomously.

get_repodcast_details

Fetches feed metadata and a list of all episodes with their IDs. This allows the AI to "read" the feed to see what's already in it.

reorder_episodes

Bulk reorders the episodes in a Repodcast feed using an array of episode IDs.

update_repodcast

Updates a feed's core metadata (name, description, imageUrl).

delete_episode

Deletes a specific episode from a feed.

update_episode

Edits a specific episode's title or description.

submit_repodcast

Submits the feed to the global PodcastIndex directory so it can be found in native podcast apps.

"Publish this feed to the Podcast Index so I can find it in Pocket Casts."


Installation & Setup

Repodify provides a high-availability cloud MCP endpoint running over Server-Sent Events (SSE). Depending on your AI client, choose the setup that fits best:

Recommended

Method 1: Cloud SSE with OAuth 2.0

For modern clients that support remote MCP servers (Claude, Cursor, Zed, Antigravity). No API key pasting required—your client will prompt you to log into Repodify via browser to authorize access automatically.

MCP Server URL:

https://repodify.app/api/mcp

Claude Desktop / Client Config (claude_desktop_config.json):

{
  "mcpServers": {
    "repodify": {
      "url": "https://repodify.app/api/mcp"
    }
  }
}

Method 2: Cloud SSE with Static API Key

If your agent runs in a headless environment or Docker container without browser access, pass your secret key from your Settings page in the HTTP headers:

{
  "mcpServers": {
    "repodify": {
      "url": "https://repodify.app/api/mcp",
      "headers": {
        "Authorization": "Bearer repodify_live_YOUR_API_KEY"
      }
    }
  }
}

Method 3: Local Stdio CLI Proxy

If your client only supports local process execution via stdio, install the official CLI proxy:

npm install -g @repodify/mcp-server
{
  "mcpServers": {
    "repodify": {
      "command": "repodify-mcp",
      "env": {
        "REPODIFY_API_KEY": "repodify_live_YOUR_API_KEY"
      }
    }
  }
}

Developer Discovery Metadata

Repodify implements the standard RFC 8414 OAuth 2.0 Authorization Server Metadata specification. Custom agent frameworks can discover our token endpoints automatically at:
https://repodify.app/.well-known/oauth-authorization-server