4,000+ servers built on vurb.ts
Vinkius

Podcast Index MCP Server for CrewAIGive CrewAI instant access to 16 tools to Get Episode By Guid, Get Episodes By Feed Id, Get Episodes By Feed Url, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Podcast Index through Vinkius, pass the Edge URL in the `mcps` parameter and every Podcast Index tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Podcast Index MCP Server for CrewAI is a standout in the Audio Music category — giving your AI agent 16 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Podcast Index Specialist",
    goal="Help users interact with Podcast Index effectively",
    backstory=(
        "You are an expert at leveraging Podcast Index tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Podcast Index "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 16 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Podcast Index
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Podcast Index MCP Server

Connect to the Podcast Index to tap into a massive, independent database of podcasts and episodes. This MCP server allows your AI agent to browse the open podcasting directory without the restrictions of proprietary platforms.

When paired with CrewAI, Podcast Index becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Podcast Index tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Deep Search — Find podcasts by general terms, specific titles, or even by the people (hosts/guests) featured in them.
  • Metadata Retrieval — Fetch comprehensive details using RSS feed URLs, Index IDs, Podcast GUIDs, or iTunes IDs.
  • Episode Discovery — List all episodes for a specific feed or find individual episodes by their unique GUID.
  • Trending & Recent — Stay updated with recent feeds and episodes, or discover something new with random episode selection.

The Podcast Index MCP Server exposes 16 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 16 Podcast Index tools available for CrewAI

When CrewAI connects to Podcast Index through Vinkius, your AI agent gets direct access to every tool listed below — spanning podcasting, directory-api, metadata-retrieval, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get episode by guid on Podcast Index

Get a specific episode by its GUID

get

Get episodes by feed id on Podcast Index

List episodes for a specific feed ID

get

Get episodes by feed url on Podcast Index

List episodes for a specific feed URL

get

Get podcast by feed id on Podcast Index

Get podcast details using its internal Index ID

get

Get podcast by feed url on Podcast Index

Get podcast details using its RSS feed URL

get

Get podcast by guid on Podcast Index

Get podcast details using its Podcast GUID

get

Get podcast by itunes id on Podcast Index

Get podcast details using its iTunes ID

get

Get random episodes on Podcast Index

Get a selection of random episodes

get

Get recent episodes on Podcast Index

Get the most recently published episodes

get

Get recent feeds on Podcast Index

Get the most recently added or updated feeds

get

Get recent new feeds on Podcast Index

Get feeds newly added to the index

get

Get value by feed id on Podcast Index

Get the value block by feed ID

get

Get value by feed url on Podcast Index

Get the value block (e.g., Lightning Network details) for a feed URL

search

Search by person on Podcast Index

Search for podcasts featuring a specific person

search

Search by term on Podcast Index

Search for podcasts by a general search term

search

Search by title on Podcast Index

Search for podcasts by title

Connect Podcast Index to CrewAI via MCP

Follow these steps to wire Podcast Index into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 16 tools from Podcast Index

Why Use CrewAI with the Podcast Index MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Podcast Index through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Podcast Index + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Podcast Index MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Podcast Index for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Podcast Index, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Podcast Index tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Podcast Index against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Podcast Index in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Podcast Index immediately.

01

"Search for podcasts about artificial intelligence using a general term."

02

"Find all podcasts featuring Lex Fridman."

03

"Get the latest episodes for the podcast with feed ID 750746."

Troubleshooting Podcast Index MCP Server with CrewAI

Common issues when connecting Podcast Index to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Podcast Index + CrewAI FAQ

Common questions about integrating Podcast Index MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →