Skip to main content
Glama

YouTube MCP

Local, read-only MCP server for YouTube Data API v3 and YouTube Analytics API.

Guides:

Features

  • Public YouTube Data API lookups with an API key.

  • OAuth-based private channel reads for the authenticated user's own channel.

  • YouTube Analytics reports for videos and channels.

  • Local stdio MCP transport with no hosted service.

Related MCP server: youtube-mcp

Security model

  • Runs locally over stdio.

  • Uses only read scopes:

    • https://www.googleapis.com/auth/youtube.readonly

    • https://www.googleapis.com/auth/yt-analytics.readonly

  • Keeps Google API keys, OAuth client files, and OAuth tokens out of Git.

  • Looks for credentials in ~/.config/youtube-mcp/ by default.

Never commit these files:

  • ~/.config/youtube-mcp/api_key.txt

  • ~/.config/youtube-mcp/client_secret.json

  • ~/.config/youtube-mcp/token.json

Google setup

  1. Create a Google Cloud project.

  2. Enable YouTube Data API v3 and YouTube Analytics API.

  3. Create an OAuth 2.0 Client ID with application type Desktop app.

  4. Download the client JSON.

  5. Save it as:

mkdir -p ~/.config/youtube-mcp
cp ~/Downloads/client_secret_*.json ~/.config/youtube-mcp/client_secret.json
chmod 600 ~/.config/youtube-mcp/client_secret.json

API key

For public YouTube Data API v3 calls, save the API key here:

mkdir -p ~/.config/youtube-mcp
printf '%s\n' 'YOUR_YOUTUBE_DATA_API_KEY' > ~/.config/youtube-mcp/api_key.txt
chmod 600 ~/.config/youtube-mcp/api_key.txt

The API key is used by:

  • youtube_search_videos

  • youtube_get_video

  • youtube_get_channel

OAuth is still required for private or account-scoped tools:

  • youtube_list_my_videos

  • youtube_get_video_analytics

  • youtube_get_channel_analytics

Run locally

From this directory:

python3 -m venv .venv
. .venv/bin/activate
python -m pip install -e .
PYTHONPATH=src python3 -m youtube_mcp.server

Example MCP config:

{
  "mcpServers": {
    "youtube": {
      "command": "python3",
      "args": ["-m", "youtube_mcp.server"],
      "env": {
        "PYTHONPATH": "/absolute/path/to/youtube-mcp/src"
      }
    }
  }
}

OAuth note

youtube_auth_url returns the Google authorization URL. Open it, approve the read-only scopes, copy the authorization code, then call youtube_auth_exchange_code with that code. The token is saved at:

~/.config/youtube-mcp/token.json

Tools

  • youtube_auth_status

  • youtube_auth_url

  • youtube_auth_exchange_code

  • youtube_search_videos

  • youtube_get_video

  • youtube_get_channel

  • youtube_list_my_videos

  • youtube_get_video_analytics

  • youtube_get_channel_analytics

Development

Run the tests with:

PYTHONPATH=src python3 -m unittest discover -s tests

License

MIT

Available Tools

9 tools
youtube_auth_exchange_codeB

Exchange a pasted OAuth authorization code for a local token file.

Inputs: code (required).

youtube_auth_statusA

Check whether local YouTube OAuth credentials and token are available.

Inputs: no named parameters.

youtube_auth_urlA

Create a Google OAuth URL using the local desktop app client secret.

Inputs: no named parameters.

youtube_get_channelC

Get snippet, statistics, and content details for a channel.

Inputs: channel_id (required).

youtube_get_channel_analyticsC

Read channel analytics metrics for the authenticated channel.

Inputs: end_date (required), start_date (required), metrics, dimensions.

youtube_get_videoC

Get snippet, statistics, and content details for a video.

Inputs: video_id (required).

youtube_get_video_analyticsC

Read analytics metrics for one authenticated-channel video.

Inputs: end_date (required), video_id (required), start_date (required), metrics.

youtube_list_my_videosC

List videos from the authenticated channel uploads playlist.

Inputs: max_results.

youtube_search_videosC

Search public YouTube videos with YouTube Data API v3.

Inputs: query (required), max_results.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct purpose: three for OAuth, two for channel data (with analytics), two for video data (with analytics), one for listing own videos, and one for public search. No overlap in functionality.

    Naming Consistency4/5

    All tools are prefixed with 'youtube_' and mostly follow a verb_resource pattern (e.g., get_channel, search_videos). However, auth tools use a resource_verb pattern (auth_exchange_code) and there is a mix of 'get_' and 'list_' for retrieval, causing minor inconsistency.

    Tool Count5/5

    With 9 tools, the server covers authentication, channel info, video info, analytics, and search without being overly large or small. The number is well-suited for a focused YouTube data and analytics MCP server.

    Completeness3/5

    The server provides read and analytics operations but lacks write capabilities (e.g., upload, update, delete videos) and playlist management. For a server named 'YouTube MCP', these are notable gaps, making it incomplete for full channel management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Streamable HTTP MCP server for YouTube that enables video search, channel exploration, playlist browsing, and video detail retrieval via the YouTube Data API.
      6
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      MCP server for YouTube Data API v3 enabling video search, channel lookup, trending content, comments, and playlist management.
      11
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local, privacy-first MCP server providing direct access to official YouTube Data, Analytics, Reporting, and Live Streaming APIs for creators, enabling channel analysis, research, and guarded management operations.
      4
      MIT