MCP Servers
conorbronsdon/op3-mcp
MCP server for OP3 podcast analytics: downloads, geography, app share. Read-only.
Our verdict
We have not reviewed conorbronsdon/op3-mcp yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About conorbronsdon/op3-mcp
A read-only MCP server that exposes OP3 podcast analytics data including download counts, geographic distribution, and app share. It uses TypeScript and provides a standardized interface for querying podcast metrics.
Best for
Developers needing programmatic access to OP3 podcast analytics in a read-only MCP format
Use cases
- Retrieve podcast download statistics for analysis
- Query geographic breakdown of podcast listeners
- Fetch app share data for podcast distribution
Notes
1 stars on GitHub. Last updated 2026-07-10. Licensed MIT.
Pros
- Provides structured access to OP3 analytics via MCP
- Read-only design reduces risk of accidental data modification
- Lightweight TypeScript implementation
Cons
- Very limited community adoption with only 1 star
- Read-only constraint may not suit all use cases
- Dependent on OP3 platform availability and API
Key facts
What we have checked
Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Tools exposed
op3_get_showop3_show_downloadsop3_episode_downloadsop3_top_appsop3_top_countriesop3_downloads_timeseries
Clients the listing names (not checked here)
Claude Desktop, Claude Code
Example client config
{
"mcpServers": {
"op3": {
"command": "npx",
"args": [
"-y",
"@conorbronsdon/op3-mcp"
],
"env": {
"OP3_API_TOKEN": "your-op3-token"
}
}
}
}Install
Add conorbronsdon/op3-mcp to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --env OP3_API_TOKEN=YOUR_OP3_API_TOKEN --transport stdio conorbronsdon-op3-mcp -- npx -y @conorbronsdon/op3-mcp@0.2.0Needs OP3_API_TOKEN: replace each YOUR_ value with your own.
Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"conorbronsdon-op3-mcp": {
"command": "npx",
"args": [
"-y",
"@conorbronsdon/op3-mcp@0.2.0"
],
"env": {
"OP3_API_TOKEN": "YOUR_OP3_API_TOKEN"
}
}
}
}Needs OP3_API_TOKEN: replace each YOUR_ value with your own.
Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"conorbronsdon-op3-mcp": {
"command": "npx",
"args": [
"-y",
"@conorbronsdon/op3-mcp@0.2.0"
],
"env": {
"OP3_API_TOKEN": "YOUR_OP3_API_TOKEN"
}
}
}
}Needs OP3_API_TOKEN: replace each YOUR_ value with your own.
VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"inputs": [
{
"type": "promptString",
"id": "op3-api-token",
"description": "OP3 API token — sign in at https://op3.dev and open your API token page",
"password": true
}
],
"servers": {
"conorbronsdon-op3-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@conorbronsdon/op3-mcp@0.2.0"
],
"env": {
"OP3_API_TOKEN": "${input:op3-api-token}"
}
}
}
}Needs OP3_API_TOKEN: replace each YOUR_ value with your own.
Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.conorbronsdon-op3-mcp]
command = "npx"
args = ["-y", "@conorbronsdon/op3-mcp@0.2.0"]
env_vars = ["OP3_API_TOKEN"]Needs OP3_API_TOKEN: replace each YOUR_ value with your own.
- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What conorbronsdon/op3-mcp connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.0Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.0Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.0Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.0Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.0Config checked | Codex docs |
Sources
Where this comes from
No sources recorded yet. Each source we check is listed here with the date we checked it.
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.