A Model Context Protocol (MCP) server that provides tools for safely interacting with public YouTube data via the official YouTube Data API v3 and OAuth 2.0.

Available Tools

The following tools are exposed to any compatible MCP client (like Claude Desktop, Cursor, or Supernova):

Tool Name	Description
`search_youtube_content`	Search public videos, channels, and playlists.
`get_video_details`	View video statistics, descriptions, and metadata.
`download_video_caption`	Download and automatically parse clear-text transcripts via `yt-dlp`.
`get_channel_details`	Inspect public channel subscriber counts and profiles.
`get_playlists`	Get public user playlists.
`get_playlist_items`	Look up videos inside a playlist.
`get_comment_threads`	Fetch top-level comment threads for a video.
`get_comments_replies`	Fetch specific comment replies.
`get_video_captions_metadata`	Fetch available caption track metadata for a video.
`get_video_categories`	Get localized video categories.
`get_supported_languages` / `Regions`	Check YouTube localization support.

(Tool capabilities matching YouTube Data API GET resources)

1. Setup Environment Variables

Create a .env file in the root directory where you are running the server.

GOOGLE_CLIENT_ID="your-google-oauth-client-id"
GOOGLE_CLIENT_SECRET="your-google-oauth-client-secret"

Acquiring Credentials

Go to the Google Cloud Console.
Create or select a project.
Enable the YouTube Data API v3.
Navigate to APIs & Services > Credentials.
Create an OAuth 2.0 Client ID (Application type: "Web application", Authorized redirect URIs: http://localhost:3000/oauth2callback).

2. Installation and Usage

To install and use this MCP server with Claude Desktop, Cursor, or Antigravity, add it to your MCP server configuration:

{
  "mcpServers": {
    "youtube-mcp": {
      "command": "npx",
      "args": ["-y", "@mrsknetwork/ytmcp"]
    }
  }
}

Local Development

Clone and Install:

git clone https://github.com/mrsknetwork/youtube-mcp.git
cd youtube-mcp
npm install

Build:
```
npm run build
```
Start the Server:
```
npm start
```

3. First-time Authentication

When you run the server for the first time, it will automatically open a Google Login page in your default browser. Authorize the application. Upon success, a tokens.json file will be generated locally so you don't continually need to authenticate.

Note: The authorization server spins up a small local express app strictly on 127.0.0.1:3000 to capture the callback securely.