How do I find my Podchaser API Key?

Log in to your [**Podchaser developer portal**](https://api.podchaser.com/), create an application, and you will find your API Token in your dashboard. Copy and paste it below.

Can I search for podcasts by host?

Yes. The search tools allow you to use host names as keywords to retrieve podcasts and creators from the Podchaser database.

Does it support episode descriptions?

Yes. The `get_podcast_details` and `list_podcast_episodes` tools retrieve detailed descriptions and show notes for podcasts and episodes.

Podchaser Podcast API MCP Server for VS Code Copilot 4 tools — connect in under 2 minutes

Name: Podchaser Podcast API
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 4 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Podchaser Podcast API and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "podchaser-podcast-api": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Podchaser Podcast API MCP Server

Empower your AI agent to orchestrate your entire audio research and podcast auditing workflow with the Podchaser Podcast API, the authoritative source for high-quality audio metadata. By connecting Podchaser to your agent, you transform complex audio searches into a natural conversation. Your agent can instantly search for thousands of podcasts, audit episode lists, and retrieve host metadata without you ever touching a podcast directory. Whether you are conducting media research or managing content distribution constraints, your agent acts as a real-time audio consultant, ensuring your data is always comprehensive and up-to-the-minute.

GitHub Copilot Agent mode brings Podchaser Podcast API data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 4 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Podcast Auditing — Search for thousands of podcasts by title or keyword and retrieve detailed metadata, including descriptions and ratings.
Episode Oversight — Audit the complete episode list for any podcast to understand the temporal distribution of audio content instantly.
Host Discovery — Retrieve detailed metadata for podcast hosts and creators to assist in deep-dive media classification.
Rating Intelligence — Query community ratings and reviews to understand the current industry lead in audio quality.
Operational Monitoring — Check API status to ensure your audio research workflow is always operational.

The Podchaser Podcast API MCP Server exposes 4 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Podchaser Podcast API to VS Code Copilot via MCP

Follow these steps to integrate the Podchaser Podcast API MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Podchaser Podcast API

Ask Copilot: "Using Podchaser Podcast API, help me...". 4 tools available

Why Use VS Code Copilot with the Podchaser Podcast API MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Podchaser Podcast API through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Podchaser Podcast API + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Podchaser Podcast API MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Podchaser Podcast API MCP Tools for VS Code Copilot (4)

These 4 tools become available when you connect Podchaser Podcast API to VS Code Copilot via MCP:

check_api_status

Check if the Podchaser service is operational

get_podcast_details

Get full metadata and social links for a specific podcast by ID

list_podcast_episodes

List all episodes for a specific podcast ID

search_podcasts

Search for podcasts by title or keywords on Podchaser

Example Prompts for Podchaser Podcast API in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Podchaser Podcast API immediately.

"Search for podcasts about 'data science' using Podchaser."

"What are the latest episodes for podcast ID '12345'?"

"Show details for podcast 'The Daily'."

Troubleshooting Podchaser Podcast API MCP Server with VS Code Copilot

Common issues when connecting Podchaser Podcast API to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Podchaser Podcast API + VS Code Copilot FAQ

Common questions about integrating Podchaser Podcast API MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.