mcpdirectory.dev
9,129 servers · updated 23 Sept

Rytdl MCP server

community Active last commit 20 d
{
  "mcpServers": {
    "dinglebear-rytdl": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/rytdl@latest"
      ],
      "env": {
        "YTDLP_TARGET_PATH": "/path/to/directory",
        "YTDLP_VIDEO_TARGET_PATH": "/path/to/directory",
        "YTDLP_REMOTE_PATH": "/path/to/directory",
        "YTDLP_VIDEO_REMOTE_PATH": "/path/to/directory",
        "YTDLP_HISTORY_PATH": "/path/to/directory",
        "YTDLP_PLEX_URL": "https://..."
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @dinglebear/rytdlversion 1.0.4

What it does

Rytdl exposes yt-dlp search, download, and metadata operations through MCP tools and a CLI. It handles audio and video downloads with proper tagging, transfer to local/SSH/rclone destinations, and optional Plex playlist integration, designed for personal media workflows with trusted callers.

  • Search YouTube and retrieve video metadata without downloading files.
  • Download audio or video from YouTube, tag the files with metadata, and transfer them to local or remote destinations.
  • Create and maintain Plex playlists from downloaded audio with fingerprinting via AcoustID/MusicBrainz.

Tools this server exposes

ToolDoes
youtube_searchSearch YouTube through yt-dlp and return result URLs without downloading media.
youtube_search_uiOpen an interactive YouTube search UI in MCP App.
youtube_probeRetrieve metadata and information about a YouTube video without downloading.
youtube_identifyIdentify audio files and fingerprint them through AcoustID/MusicBrainz.
youtube_downloadDownload audio, video, or both from YouTube into a staging tree with metadata tagging.
youtube_statsRetrieve download statistics and ledger information.
youtube_plex_playlistBuild and sync Plex playlists from download history.
youtube_transfer_queueDrain server-made retained-staging transfer manifests.

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.