# Podstatus MCP server
> Query podcast rankings, reviews, tracked keywords and analytics from Apple Podcasts, Spotify and iVoox.
- Listing: https://mcp.tc/i/podstatus
- Connect: use the server's own URL `https://podstatus.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: Podstatus
- Homepage:
## About
Connects an AI assistant to a Podstatus account so it can read podcast chart rankings, listener reviews, tracked keywords, reports and analytics. It covers Apple Podcasts, Spotify and iVoox, and can compare chart history, summarize reviews and help draft client updates. OP3 download analytics are available when connected.
Runs as a hosted Streamable HTTP endpoint at https://podstatus.com/mcp. Access needs a Podstatus account. Sign-in uses OAuth 2.0 with PKCE, or a scoped API key can be used instead. Access is read-only by default.
## What it can do
- Read podcast chart rankings and history across Apple Podcasts, Spotify and iVoox
- Summarize listener reviews
- Check tracked keyword positions
- Read reports and analytics
- Access OP3 download analytics when connected
- Draft client updates from ranking data
## Example prompts
- "How did my podcast rank on Apple Podcasts in Spain this month?"
- "Summarize the new listener reviews from the last week."
- "Compare my Spotify and Apple chart history for the last 30 days."
- "Draft a client update using this week's rankings and keyword changes."
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http podstatus https://podstatus.com/mcp
```
2. Start Claude Code, type `/mcp`, pick **podstatus** and choose **Authenticate**. A browser window opens for the Podstatus sign-in.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.
2. Name it **Podstatus** and paste this URL:
```url
https://podstatus.com/mcp
```
3. Click **Add**, then **Connect**, and sign in when Podstatus asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://podstatus.com/mcp` and click **Add**.
3. Click **Connect** and sign in when Podstatus asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.
2. Enter a name for the server.
3. Under **Connection**, paste `https://podstatus.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Podstatus to sign in.
4. Check **I understand and want to continue**, then select **Create as a plugin**.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"podstatus": {
"url": "https://podstatus.com/mcp"
}
}
}
```
Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"podstatus","type":"http","url":"https://podstatus.com/mcp"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"podstatus": {
"type": "http",
"url": "https://podstatus.com/mcp"
}
}
}
```
VS Code asks you to sign in the first time the server starts.
### Devin Desktop
1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):
`mcp_config.json`:
```json
{
"mcpServers": {
"podstatus": {
"serverUrl": "https://podstatus.com/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add podstatus --url https://podstatus.com/mcp
codex mcp login podstatus
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.podstatus]
url = "https://podstatus.com/mcp"
```
### Gemini CLI
```bash
gemini mcp add --transport http podstatus https://podstatus.com/mcp
```
Then, inside Gemini CLI, run `/mcp auth podstatus` to sign in.
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"podstatus": {
"type": "http",
"url": "https://podstatus.com/mcp"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://podstatus.com/mcp`.
## Details
- Last checked: 2026-11-15 (reachable, asks for credentials)
- Listed: 2026-11-11
- Updated: 2026-11-11
---
Source: https://mcp.tc/i/podstatus (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report