YTDL RMCP

Rust MCP server and CLI for yt-dlp search, downloads, metadata, transfers, and Plex playlists.

YTDL RMCP is a Rust-implemented MCP server and CLI tool that wraps yt-dlp to provide media search, downloads, metadata operations, file transfers, and Plex playlist management. It communicates over stdio transport, making it suitable for use with AI agent frameworks that support the MCP protocol. The server is distributed as an npm package at version 1.0.2 under the publisher ai.dinglebear, with source available at the linked GitHub repository.

Configuration is handled through environment variables. YTDLP_PLEX_URL and YTDLP_PLEX_TOKEN are used to connect the server to a Plex Media Server instance, enabling playlist creation and management. YTDLP_ACOUSTID_CLIENT_KEY supports AcoustID-based audio fingerprinting or identification workflows. YTDL_RMCP_BINARY_VERSION and YTDL_RMCP_RELEASE_BASE_URL control which binary release is fetched, and RUST_LOG adjusts logging verbosity.

Because no specific MCP tools are exposed in the registry record, the exact set of callable tool endpoints is not confirmed here. Based on the declared capabilities — search, downloads, metadata, transfers, and Plex playlists — agents using this server would be able to orchestrate yt-dlp-based media workflows programmatically. It is not a database integration and is unrelated to Postgres or SQL operations. It requires a working yt-dlp binary and, for Plex features, a running Plex Media Server with a valid API token.

Use cases

  • Download media via yt-dlp from within an AI agent workflow
  • Retrieve metadata for online video or audio content
  • Manage Plex playlists automatically after media downloads
  • Transfer downloaded media files as part of an automated pipeline
  • Search for media content through yt-dlp from an MCP-compatible agent

When to use it

  • When an AI agent needs to automate yt-dlp-based media downloads over MCP
  • When Plex playlist management should be integrated into an agent workflow
  • When stdio MCP transport is the required communication method

When not to use it

  • When looking for a Postgres or any database MCP server — this has no database functionality
  • When the deployment environment cannot run a Rust binary or install npm packages
  • When Plex integration is needed but no Plex Media Server instance is available
  • When the MCP client requires a transport other than stdio
  • When yt-dlp is not installed or accessible in the target environment