mcpdirectory.dev
9,129 servers · updated 23 Sept

Youtube Transcript And Youtube Search MCP server

community Active last commit 30 d
{
  "mcpServers": {
    "transcriptout-youtube-transcript-and-youtube-search": {
      "type": "http",
      "url": "https://api.transcriptout.com/mcp"
    }
  }
}
file .mcp.json (in your project root)version 1.0.1

What it does

This server lets AI agents read YouTube videos by providing transcripts in multiple formats, search YouTube for videos and channels, list playlists, and submit bulk transcript jobs. It's for developers building agents that need to work with YouTube content.

  • Get a transcript of a YouTube video so an agent can summarize or extract information from it.
  • Search YouTube for videos or channels by query to find relevant content programmatically.
  • Submit a background job to transcribe thousands of videos and retrieve them later for batch processing.

Tools this server exposes

ToolDoes
get_transcriptFetch the transcript of a YouTube video in text or JSON format with optional language specification.
search_videosSearch YouTube for videos by query string.
search_channelsSearch YouTube for channels by query string.
get_channel_videosList videos from a YouTube channel.
get_playlist_videosList videos from a YouTube playlist.
submit_bulk_jobSubmit a background job to transcribe up to 4,000 videos.
get_bulk_job_statusCheck the status of a submitted bulk transcript job.
get_bulk_job_resultsRetrieve results from a completed bulk transcript job.
list_bulk_jobsList all bulk transcript jobs associated with your account.
chunk_transcriptSplit a transcript into chunks with word-level timestamps for RAG workflows.
get_video_metadataGet metadata for a YouTube video including title, duration, and channel information.
get_channel_infoGet information about a YouTube channel.
get_playlist_infoGet information about a YouTube playlist.
validate_urlValidate whether a given URL is a valid YouTube video, channel, or playlist link.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.