Skip to main content
Glama
mcp-youtube-intelligence

mcp-youtube-intelligence

by Dmitriusan

mcp-youtube-intelligence

MCP server for extracting structured intelligence from YouTube channels and videos.

What it does

Analyzes YouTube channels to produce structured intelligence reports:

  • Transcript extraction across recent videos (up to 50 videos)

  • Semantic topic extraction per video via Gemini (theme, named entities, tags)

  • Keyword frequency analysis across all transcripts (fallback when Gemini is unavailable)

Related MCP server: MCP YouTube Intelligence

Prerequisites

You need API keys for three services:

Variable

Where to get it

YOUTUBE_API_KEY

Google Cloud Console → YouTube Data API v3

APIFY_TOKEN

Apify Console → Account → Integrations → API token

GEMINI_API_KEY

Google AI Studio → Get API key

GEMINI_API_KEY is optional — if omitted, the tool falls back to word-frequency topic extraction instead of semantic analysis. The same fallback applies when a configured Gemini call fails (invalid key, exhausted quota, blocked content); the result's note says why.

Optional

Variable

Default

Description

ANALYZE_CHANNEL_OUTPUT_DIR

./output/

Directory where per-channel JSON analysis artifacts are written

Installation

npm install -g mcp-youtube-intelligence

CLI flags

mcp-youtube-intelligence --version   # or -v — print the installed version and exit
mcp-youtube-intelligence --help      # or -h — print usage and exit

Running the command with no flags starts the MCP server itself (stdio transport) — this is what an MCP client config invokes; it's not meant to be run bare in a terminal for interactive use.

Usage

Add to your Claude Desktop / MCP client config:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Linux: ~/.config/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "youtube-intelligence": {
      "command": "mcp-youtube-intelligence",
      "env": {
        "YOUTUBE_API_KEY": "your-youtube-api-key",
        "APIFY_TOKEN": "your-apify-token",
        "GEMINI_API_KEY": "your-gemini-api-key"
      }
    }
  }
}

Tools

analyze_channel — Extract intelligence from a YouTube channel

channel_url: YouTube channel URL or @handle. Accepts:
               - @handle (e.g. @fireship)
               - full URL with handle (e.g. youtube.com/@fireship)
               - /channel/UC... URL
               - bare 24-character UC... channel ID
               - legacy /c/name or /user/name URL
max_videos:  Number of recent videos to analyze (default: 5, max: 50)

Returns a JSON object:

Field

Meaning

channel_id, channel_title

The resolved channel

channel_url

Your channel_url input, echoed back

sample_video_ids

The most recent uploads that were analyzed

videos_analyzed

How many videos were fetched from the channel's uploads playlist

transcripts_available

How many of those came back with caption content

topics

Up to 20 top keywords by frequency across all transcripts. Always computed

topics_structured

Per video: theme, entities[], tags[] from Gemini. Empty when Gemini is not configured or fails. Only the first 1,000 words of each transcript are sent, and a video Gemini blocks or returns nothing usable for is left out

note

Which analysis mode ran. When Gemini was configured but failed, it also says why

output_path

Where the JSON artifact was written. Absent if the write failed

Example prompt: "Analyze the @fireship YouTube channel and tell me what topics they cover most."

Development

npm install
npm run build
npm test

License

MIT

Available Tools

1 tool
analyze_channelA

Analyze a YouTube channel and return a JSON object with: channel_id, channel_title, channel_url, sample_video_ids[], videos_analyzed (count of videos fetched from playlist), transcripts_available (count with actual caption content), topics[] (top keyword frequencies across all transcripts), topics_structured[] (per-video semantic analysis — each entry has video_id/theme/entities[]/tags[]), note (which analysis mode ran), and optional output_path (local artifact path). Requires YOUTUBE_API_KEY and APIFY_TOKEN; set GEMINI_API_KEY for topics_structured semantic analysis (falls back to keyword-only when absent). Supported channel inputs: @handle (e.g. @fireship), youtube.com/@handle URL, /channel/UC... URL, bare 24-char UCxxxxxx ID, or legacy /c/ and /user/ URLs.

Inputs: channel_url (required), max_videos.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion with other tools.

    Naming Consistency5/5

    The single tool name 'analyze_channel' follows a clear verb_noun pattern, making it predictable and unambiguous.

    Tool Count2/5

    With only one tool for a domain like YouTube intelligence, the surface is too narrow; typical well-scoped servers have 3-15 tools.

    Completeness2/5

    The server only offers channel analysis, missing obvious operations like video search, video details, playlist management, and subscription handling, leaving significant gaps.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for intelligent YouTube video analysis that provides token-optimized summaries, sentiment analysis, and entity extraction from transcripts. It enables AI assistants to perform video reporting, channel monitoring, and comprehensive YouTube searches through structured data tools.
      10
      53
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Production-grade Model Context Protocol server for YouTube intelligence. Extract, analyze, and automate insights from YouTube channels and videos using the official YouTube Data API v3. Built for AI agents, automation pipelines, and content intelligence workflows.
      16
      1
      MIT